Stephen Hemminger wrote:
On Tue, 29 Jan 2008 03:46:08 +0300
Michael Tokarev [EMAIL PROTECTED] wrote:
[]
There are 2 drivers for 8139-based NICs. For really different two kinds
of hardware, which both uses the same PCI identifiers. Both drivers
claims to work with all NICs with those PCI
On Tuesday 29 January 2008 11:43:53 Michael Tokarev wrote:
Stephen Hemminger wrote:
On Tue, 29 Jan 2008 03:46:08 +0300
Michael Tokarev [EMAIL PROTECTED] wrote:
[]
There are 2 drivers for 8139-based NICs. For really different two kinds
of hardware, which both uses the same PCI
On Jan 29 2008 18:34, Jon Masters wrote:
On Tue, 2008-01-29 at 03:46 +0300, Michael Tokarev wrote:
Udev in fact loads both - 8139cp and 8139too. The difference is the ORDER
in which it loads them - if for cp-handled hardware it first loads too,
too will complain as above and will NOT claim
On Tue, 2008-01-29 at 03:46 +0300, Michael Tokarev wrote:
Udev in fact loads both - 8139cp and 8139too. The difference is the ORDER
in which it loads them - if for cp-handled hardware it first loads too,
too will complain as above and will NOT claim the device. The same is
true for the
Linux 2.6.24 kernel gives the following messages when udev coldplugging
loads the driver for my NIC:
8139too :00:0b.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip
8139too :00:0b.0: Use the 8139cp driver for improved performance and
stability.
ACPI: PCI Interrupt Link [LNK1]
Frederik Himpe wrote:
Linux 2.6.24 kernel gives the following messages when udev coldplugging
loads the driver for my NIC:
8139too :00:0b.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip
8139too :00:0b.0: Use the 8139cp driver for improved performance and
stability.
There
On Tue, 29 Jan 2008 03:46:08 +0300
Michael Tokarev [EMAIL PROTECTED] wrote:
Frederik Himpe wrote:
Linux 2.6.24 kernel gives the following messages when udev coldplugging
loads the driver for my NIC:
8139too :00:0b.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip
8139too
