b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	Pavel Roskin <proski@gnu.org>,
	b43-dev@lists.infradead.org
Subject: [PATCH 1/3] b43: replace DMA translation workarounds with just a one, commented
Date: Wed, 20 Jul 2011 10:55:40 +0200	[thread overview]
Message-ID: <20110720105540.1c9d072c@maggie> (raw)
In-Reply-To: <CACna6rwMe9-dHANpDLko5yy5wu521YTGXmqBr1JYh18tYt+Z4A@mail.gmail.com>

On Wed, 20 Jul 2011 08:16:08 +0200
Rafa? Mi?ecki <zajec5@gmail.com> wrote:

> W dniu 20 lipca 2011 01:15 u?ytkownik Michael B?sch <m@bues.ch> napisa?:
> > On Wed, 20 Jul 2011 00:12:20 +0200
> > Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> >> + ? ? ? ? ? ? ?* be fixed on ssb side, but requires testing with b43,
> >> + ? ? ? ? ? ? ?* b43legacy and b44. */
> >
> > No it doesn't. b44 and b43legacy don't use 64bit DMA.
> > Just fix it in ssb, please.
> 
> They (drivers) don't, but what if we start giving them routing for
> 64-bit DMA? AFAIU they treat 64-bit DMA as 32-bit one (according to
> specs: "If 64 Bit isn't an option, Silicon Backplane and PCI-E buses
> can use 32 bit DMA.").
> 
> Won't they start using 64-bit DMA in the 32-bit way but with 64-bit
> routing bits?
> 

I have no idea what you're talking about.
The fact is: These "temporary workarounds" tend to stay in the driver forever
if we don't fix it _now_. So please fix it now.
We know whether we are on 64bit DMA or not. So if we are on 64bit DMA, use the 64bit mask.
Simply pass the "32 or 64 bit" boolean flag to ssb_dma_translation() as parameter.
There's nothing that can go wrong here with older drivers.

  parent reply	other threads:[~2011-07-20  8:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 22:12 [PATCH 0/3] b43 & bcma: DMA special (translation) bits Rafał Miłecki
2011-07-19 22:12 ` [PATCH 1/3] b43: replace DMA translation workarounds with just a one, commented Rafał Miłecki
2011-07-19 22:53   ` Larry Finger
2011-07-19 23:15   ` Michael Büsch
2011-07-20  6:16     ` Rafał Miłecki
2011-07-20  8:30       ` Larry Finger
2011-07-20  8:55       ` Michael Büsch [this message]
2011-07-20 11:10         ` Rafał Miłecki
2011-07-20 15:35           ` Michael Büsch
     [not found]             ` <4E28422C.60209@gnu.org>
2011-07-21 15:33               ` Rafał Miłecki
2011-07-21 19:34                 ` Michael Büsch
2011-07-21 21:22                   ` Michael Büsch
2011-07-21 21:31                     ` Rafał Miłecki
2011-07-21 21:40                       ` Michael Büsch
2011-07-21 21:49                         ` Larry Finger
     [not found]                   ` <4E2A7B59.80106@gnu.org>
2011-07-23  8:21                     ` Michael Büsch
2011-07-19 22:12 ` [PATCH 2/3] bcma: inform drivers about translation bits needed for the core Rafał Miłecki
2011-07-19 22:12 ` [PATCH 3/3] b43: bcma: get DMA translation bits Rafał Miłecki

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=20110720105540.1c9d072c@maggie \
    --to=m@bues.ch \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=proski@gnu.org \
    --cc=zajec5@gmail.com \
    /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).