[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1JKOBl-0007ne-EE@faramir.fjphome.nl>
Date: Thu, 31 Jan 2008 02:26:01 +0100
From: Frans Pop <elendil@...net.nl>
To: Adrian Bunk <bunk@...nel.org>
Cc: akpm@...ux-foundation.org, auke-jan.h.kok@...el.com,
davem@...emloft.net, jeff@...zik.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, randy.dunlap@...cle.com,
torvalds@...ux-foundation.org
Subject: Re: Mostly revert "e1000/e1000e: Move PCI-Express device IDs over to e1000e"
Adrian Bunk wrote:
>> Jeff, Auke, would something like this be acceptable? It makes it very
>> obvious in the driver table which entries are for the PCIE versions that
>> would be handled by the E1000E driver if it is enabled..
>
> I don't like it:
> We should aim at having exactly one driver for one card.
There is one thing I don't understand, but that may well be just me...
>From Linus' original patch:
> +++ b/drivers/net/e1000/e1000_main.c
> + INTEL_E1000_ETHERNET_DEVICE(0x108C),
So, apparently support for 8086:108c was removed from the e1000 driver.
>From my lspci:
$ lspci -nn | grep Ether
01:00.0 Ethernet controller [0200]: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) [8086:108c] (rev 03)
But when I look at where that card is sitting:
$ readlink pci/devices/0000\:01\:00.0/driver
../../../../bus/pci/drivers/e1000
So, it's on the PCI bus, not on the PCI-Express bus (which I also have, but
which has no devices on it).
Or does the e1000e driver also support cards on the PCI bus?
If that's the case then the original changelog entry "Move PCI-Express
device IDs over to e1000e" is misleading as it's not only PCI-Express
devices...
Hmmm. Or does which driver is loaded decide on which bus the device ends up?
Confused,
FJP
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists