From: Francois Romieu <romieu@fr.zoreil.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Andi Kleen <ak@muc.de>, netdev@oss.sgi.com
Subject: Re: [PATCH 1/5] r8169: auto detect 32-bit slot
Date: Thu, 10 Mar 2005 00:08:09 +0100 [thread overview]
Message-ID: <20050309230809.GC9502@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20050309135530.5c5c80b6@dxpl.pdx.osdl.net>
Stephen Hemminger <shemminger@osdl.org> :
[...]
> I tested on old Celeron with Netgear card. I could try Amd and/or Xeon
> if you want.
If the systems are 64 bit, one would need to know how the driver behaves
when DAC is forced and:
1) the Netgear card is in a 32 bit slot, dma to highmem is enabled and used
2) the Netgear card is in a 32 bit slot, dma to highmem is enabled and unused
3) the Netgear card is in a 32 bit slot, dma to highmem is disabled
4) the Netgear card is in a 64 bit slot, dma to highmem is enabled and used
5) the Netgear card is in a 64 bit slot, dma to highmem is enabled and unused
6) the Netgear card is in a 64 bit slot, dma to highmem is disabled
+ the content of the Config2 register for 1-6.
If the amd64 hosts a built-in 8169, add the behavior with highmem disabled or
enabled + variable amount of memory.
As it still leaves some archs in the cold + DAC ought not to be dependant
on the bus width + a few "broken" adapters exist, the patch makes me a bit
sceptical.
--
Ueimor
next prev parent reply other threads:[~2005-03-09 23:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 19:29 [PATCH 1/5] r8169: auto detect 32-bit slot Stephen Hemminger
2005-03-09 19:47 ` Jeff Garzik
2005-03-09 20:16 ` Andi Kleen
2005-03-09 21:40 ` Francois Romieu
2005-03-09 21:55 ` Stephen Hemminger
2005-03-09 23:08 ` Francois Romieu [this message]
2005-03-09 23:16 ` Stephen Hemminger
2005-03-09 23:20 ` Andi Kleen
2005-03-10 0:45 ` Francois Romieu
2005-03-09 22:08 ` Jon Mason
2005-03-09 22:39 ` Francois Romieu
2005-03-10 4:14 ` Jon Mason
2005-03-10 11:17 ` Francois Romieu
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=20050309230809.GC9502@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=ak@muc.de \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).