From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org
Subject: [PATCH 1/3] b43: replace DMA translation workarounds with just a one, commented
Date: Thu, 21 Jul 2011 19:34:40 +0000 [thread overview]
Message-ID: <20110721193440.2baeaae3@Nokia-N900> (raw)
In-Reply-To: <CACna6rz+t=ZOSiK+7weN7onZh3z44QeZSiuwY2L3oSxRneFV8A@mail.gmail.com>
On Thu, 21 Jul 2011 17:33:51 +0200
Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> 2011/7/21 Pavel Roskin <proski@gnu.org>:
> > On 07/20/2011 11:35 AM, Michael B?sch wrote:
> >>
> >> On Wed, 20 Jul 2011 13:10:55 +0200
> >> Rafa? Mi?ecki<zajec5@gmail.com> ?wrote:
> >>
> >>> Sorry, for not explaining this well eno
> >>> ugh. I'm afraid of situation where b44 driver supports 64-bit DMA
> >>> device *without* handling this as such a device.
> >>
> >> A b44 or b43legacy device with 64bit DMA engine does not exist.
> >
> > There are many references to "B43legacy_DMA_64BIT" and "dma64_ops" in
> > b43legacy. ?I guess they all are unneeded, and so is struct
> > b43legacy_dma_ops.
> >
> > b44 doesn't seem to have DMA64 support. ?By the way, the result of
> > ssb_dma_translation() is placed into bp->dma_offset. ?I think the word
> > "offset" is misleading.
>
> Thanks for comment. I didn't have any time to review (&clean?)
> b43legacy, not to mention b44. Unfortunately I'm too busy with b43
> stuff for now. If you have some free time, you're input to the drivers
> is welcome :)
>
For historical reasons there is unused 64bit dma code in b43legacy. I'm not sure whether it would even work. Probably not. Larry's fixes were most likely not ported over.
next prev parent reply other threads:[~2011-07-21 19:34 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
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 [this message]
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=20110721193440.2baeaae3@Nokia-N900 \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.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