RE: [Xen-ia64-devel] eepro100 HVM NIC

["Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>]

>
>
>   I spent some time porting the eepro100 device device model
>from qemu
>into Xen.  It seems to work ok for Linux guests, but I can't
>get it
>working for Windows.  The qemu driver supports three models of
>the card:
>i82551, i82557b, and i82559er.  The i82557b is definitely
>recognized by
>the i8255x driver that ships with Windows server 2003.  The
>other two
>just show up as unknown devices in the device manager.  The most
>obvious
>thing keeping it from working seems to be that Windows remaps
>the PCI
>BARs to invalid addresses (the reason I was investigating the
>memmap,
>but that didn't help).  I don't understand why it's doing this,
>but I'll
>post the port of the eepro100 driver here to save anyone who
>wants to
>play with it the trouble.  FWIW, I also tried the Windows IPF
>driver
>available from Intel's website, but it didn't recognize any of
>the
>models as a PRO series NIC and refused to install.  Thanks,
>

Hi Alex:
        I also work on this task. Base on the primary emulator in QEMU, I 
refine it to fix where I think it doesn't
follow intel's eepr100 spec. Current status are:
1. it works for linux guest both in XEN/IPF and QEMU. But seems
speed is slow.
2. From microsoft's WDK I get a rough eepro100 driver of win2k3.
With this driver, the emulator can work in win2k3/X86 in QEMU.
3. The windows device manager can recognize the card both in QEMU and XEN/IPF. 
But it reports there is a resource conflict that
makes card can't work.

All my works base on a native i82557b card.

Now I try to use windbg to investigate into it. I am enabling windbg for IPF 
guest now, hope it helpful. Attachment is my version of eepro100.

Attachment: my_eepro100.c
Description: my_eepro100.c

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel