linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Larry Finger <Larry.Finger@lwfinger.net>, Christoph Hellwig <hch@lst.de>
Cc: linuxppc-dev@lists.ozlabs.org,
	Christian Zigotzky <chzigotzky@xenosoft.de>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [BISECTED REGRESSION] b43legacy broken on G4 PowerBook
Date: Wed, 12 Jun 2019 08:46:30 +1000	[thread overview]
Message-ID: <0b257651bb7ac4a6f0a8dce5470120b7701720b9.camel@kernel.crashing.org> (raw)
In-Reply-To: <5aaa600b-5b59-1f68-454f-20403c318f1a@lwfinger.net>

On Tue, 2019-06-11 at 17:20 -0500, Larry Finger wrote:
> b43-pci-bridge 0001:11:00.0: dma_direct_supported: failed (mask =
> 0x3fffffff, 
> min_mask = 0x5ffff000/0x5ffff000, dma bits = 0x1f

Ugh ? A mask with holes in it ? That's very wrong... That min_mask is
bogus.

Ben.



  parent reply	other threads:[~2019-06-11 22:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 22:50 [BISECTED REGRESSION] b43legacy broken on G4 PowerBook Aaro Koskinen
2019-06-06  0:54 ` Benjamin Herrenschmidt
2019-06-06  9:31   ` Aaro Koskinen
2019-06-06 10:56     ` Benjamin Herrenschmidt
2019-06-06 10:57       ` Benjamin Herrenschmidt
2019-06-06 11:43         ` Christoph Hellwig
2019-06-06 19:26           ` Larry Finger
2019-06-06 20:11           ` Larry Finger
2019-06-06  3:06 ` Larry Finger
2019-06-06  6:40   ` Christoph Hellwig
2019-06-07 17:25 ` Larry Finger
2019-06-07 17:29   ` Christoph Hellwig
2019-06-07 18:50     ` Larry Finger
2019-06-08 21:52     ` Larry Finger
2019-06-10  8:18       ` Christoph Hellwig
2019-06-10 16:09         ` Larry Finger
2019-06-11  6:05           ` Christoph Hellwig
2019-06-11 22:20             ` Larry Finger
2019-06-11 22:46               ` Aaro Koskinen
2019-06-12  1:57                 ` Larry Finger
2019-06-11 22:46               ` Benjamin Herrenschmidt [this message]
2019-06-12  1:52                 ` Larry Finger
2019-06-12  3:32                   ` Benjamin Herrenschmidt
2019-06-12  6:55               ` Christoph Hellwig
2019-06-12 19:41                 ` Larry Finger
2019-06-12 21:59                   ` Benjamin Herrenschmidt
2019-06-13  7:29                     ` Christoph Hellwig
2019-06-11 17:48           ` Andreas Schwab
2019-06-08  4:21   ` Benjamin Herrenschmidt
2019-06-08  7:23     ` Christoph Hellwig
2019-06-10 18:44     ` Larry Finger
2019-06-11  5:56       ` Benjamin Herrenschmidt
2019-06-11  6:08         ` Christoph Hellwig
2019-06-11  6:58           ` Benjamin Herrenschmidt
2019-06-11  6:59             ` Benjamin Herrenschmidt
2019-06-11  7:54               ` Christoph Hellwig
2019-06-11  9:04                 ` Benjamin Herrenschmidt
2019-06-11  7:53             ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0b257651bb7ac4a6f0a8dce5470120b7701720b9.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=aaro.koskinen@iki.fi \
    --cc=chzigotzky@xenosoft.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).