Device recognition on Intel mainboard SE7520BD2

Tom Alsberg alsbergt at cs.huji.ac.il
Sat Jan 14 10:34:19 PST 2006


On Sat, Jan 14, 2006 at 07:06:28PM +0100, Petr Murmak wrote:
> Problem is that this mainboard has 2 Intel PRO/1000 Network
> interfaces

As far as I recall (having a while ago looked at the specifications
of all new Intel Server Boards (SE7[53]2[05]..), and as shown from
your output of pciconf -lv, there is only one Intel PRO/1000
interface, and the other interface (on those boards with two
interfaces) is a Marvell Yukon chip on the PCI Express bus, as you can
see on pci5:0:0.

I am not sure of the current status, but last time I have checked
(FreeBSD 5.3 times), IIRC, there was some experimental driver for that
chip.  But now the latest I can see is a binary-only FreeBSD 5.4
driver from Marvell's site, after agreeing to some license:

http://www.marvell.com/drivers/driverDisplay.do?dId=131&pId=34

I wondered why Intel did not put two PRO/1000 interfaces but has
chosen to put a Yukon as the second interface.  It was suggested to me
that Intel believed the Yukon to be able to provide better throughput
as it is connected to the PCI-Express bus - however Intel have their
own (also called PRO/1000, so I'd assume some similarity, but can
never be sure) Gigabit Ethernet chips for PCI-Express, so I do not
understand this.  Someone shed some light on this?

  -- Tom

> none5 at pci5:0:0: class=0x020000 card=0x50218086 chip=0x436111ab rev=0x17 hdr=0x00
>     vendor   = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
>     device   = '88E8036 Marvell Yukon -EC 88E8050 PCI Express Gigabit
> Ethernet Controller'
>     class    = network
>     subclass = ethernet

> em0 at pci7:4:0:   class=0x020000 card=0x34398086 chip=0x10768086 rev=0x05 hdr=0x00
>     vendor   = 'Intel Corporation'
>     device   = '82547EI Gigabit Ethernet Controller'
>     class    = network
>     subclass = ethernet

-- 
  Tom Alsberg - certified insane, complete illiterate.
	Homepage: http://www.cs.huji.ac.il/~alsbergt/
  * An idea is not responsible for the people who believe in it.


More information about the freebsd-stable mailing list