Date: Wed, 10 Jun 2009 00:06:48 +0200 From: Juergen Lock <nox@jelal.kn-bremen.de> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: Re: flash10 vs f10; em(4) now broken in -current in qemu/vbox Message-ID: <20090609220648.GA14714@triton.kn-bremen.de> In-Reply-To: <2a41acea0906091412k4fc58f4dt2c4ebbbb6dbd46dd@mail.gmail.com> References: <20090606162235.GA49444@triton.kn-bremen.de> <2a41acea0906091104q17aeb174l8a34bf7464a80509@mail.gmail.com> <20090609195141.GA4982@triton.kn-bremen.de> <2a41acea0906091412k4fc58f4dt2c4ebbbb6dbd46dd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090609220648.GA14714>