Re: flash10 vs f10; em(4) now broken in -current in qemu/vbox

Thanks for the feedback.

I know nothing about vbox, I had assumed it followed vmware in emulating the
82545.  So, can you not configure things so you always use the type with the
workaround? I have no intention of adding workarounds to more hardware
types.

Jack



On Tue, Jun 9, 2009 at 3:06 PM, Juergen Lock <nox_at_jelal.kn-bremen.de> wrote:

> On Tue, Jun 09, 2009 at 02:12:12PM -0700, Jack Vogel wrote:
> > Your change would work, but as its shared code and there are other OS's
> and
> > their issues to worry about, what I am going to do is a bit different. I
> am
> > including
> > a patch if you would try this now, there will be a full driver update
> soon.
> >
> > Anyone set up to test this please post your results here.
>
> Ok, worked in qemu, and worked in vbox with two of the three e1000 choices;
> vbox calls the failed one Intel PRO/1000 T Server (82543GC), pciconf -lv
> says:
>
> em0_at_pci0:0:3:0: class=0x020000 card=0x10048086 chip=0x10048086 rev=0x02
> hdr=0x00
>    vendor     = 'Intel Corporation'
>    device     = '82543GC Gigabit Ethernet Controller (Copper)'
>    class      = network
>    subclass   = ethernet
>
>  Thanx,
>         Juergen
>