From: "David S. Miller" <davem@redhat.com>
To: Pekka Pietikainen <pp@ee.oulu.fi>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Dealing with buggy hardware (was: b44 and 4g4g)
Date: Sat, 5 Jun 2004 13:19:23 -0700 [thread overview]
Message-ID: <20040605131923.232f8950.davem@redhat.com> (raw)
In-Reply-To: <20040605200643.GA2210@ee.oulu.fi>
On Sat, 5 Jun 2004 23:06:44 +0300
Pekka Pietikainen <pp@ee.oulu.fi> wrote:
> + if(virt_to_bus(skb->data) + skb->len > B44_PCI_DMA_MAX) {
You can't use this non-portable interface, you have to:
1) pci_map the data
2) test the dma_addr_t returned
next prev parent reply other threads:[~2004-06-05 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-31 20:21 b44 and 4g4g Pekka Pietikainen
2004-06-05 20:06 ` Dealing with buggy hardware (was: b44 and 4g4g) Pekka Pietikainen
2004-06-05 20:19 ` David S. Miller [this message]
2004-06-09 12:29 ` Pekka Pietikainen
2004-06-10 20:05 ` Pavel Machek
2004-06-10 20:34 ` Pekka Pietikainen
2004-06-10 21:12 ` Pavel Machek
2004-06-11 6:17 ` Pekka Pietikainen
2004-06-11 9:45 ` Pavel Machek
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=20040605131923.232f8950.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pp@ee.oulu.fi \
/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).