From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: ak@suse.de
Subject: Re: X86_64 + VIA + 4g problems
Date: Mon, 02 Jan 2006 13:18:05 -0600 [thread overview]
Message-ID: <43B97C6D.7010902@shaw.ca> (raw)
In-Reply-To: <5qAKf-7n4-19@gated-at.bofh.it>
Andi Kleen wrote:
> When you not compile in the SKGE network driver does everything else work?
> skge supports 64bit DMA, so it shouldn't use any IOMMU.
Are you sure this is skge? Anyway, even if the driver does support
64-bit DMA, I would be surprised if a desktop motherboard had the
Ethernet chip connected via a 64-bit PCI bus.
This brings up something I've been wondering. It's possible to run most
64-bit capable PCI devices in a 32-bit slot (i.e. with the 64-bit part
hanging out of the slot). In this configuration the device will not be
able to use 64-bit DMA (unless it supports dual address cycle). However,
who is supposed to detect this and know to not try to use DMA addresses
above 4GB on that device? Is the driver supposed to know this and use a
32-bit DMA mask, or is the PCI subsystem able to figure this out
somehow? What if the driver has no way to detect this? I don't think
I've seen any code in the kernel that would figure out if the current
configuration of the card is actually capable of 64-bit DMA or not.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-01-02 19:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5qvTv-8f-17@gated-at.bofh.it>
[not found] ` <5qAKf-7n4-19@gated-at.bofh.it>
2006-01-02 19:18 ` Robert Hancock [this message]
2006-01-02 19:53 ` X86_64 + VIA + 4g problems Andi Kleen
2006-01-02 20:15 ` Robert Hancock
2006-01-02 20:39 ` Andi Kleen
[not found] ` <5qBcJ-7ZZ-5@gated-at.bofh.it>
[not found] ` <5qDez-2Qf-19@gated-at.bofh.it>
[not found] ` <5r2nz-63n-233@gated-at.bofh.it>
2006-01-04 3:03 ` Robert Hancock
2006-01-02 11:09 Dieter Stüken
2006-01-02 12:26 ` Carsten Otto
2006-01-02 16:22 ` Andi Kleen
2006-01-02 16:52 ` Carsten Otto
2006-01-02 17:46 ` Carsten Otto
2006-01-02 19:01 ` Andi Kleen
2006-01-03 22:54 ` Carsten Otto
2006-01-03 10:04 ` Dieter Stüken
2006-01-03 13:58 ` Andi Kleen
2006-01-03 19:56 ` Dieter Stüken
2006-01-03 21:08 ` Dieter Stüken
2006-01-03 21:26 ` Andi Kleen
2006-01-04 10:27 ` Dieter Stüken
2006-01-04 10:57 ` Andi Kleen
2006-01-04 10:57 ` Dieter Stüken
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=43B97C6D.7010902@shaw.ca \
--to=hancockr@shaw.ca \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.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