qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [6490] Update #defines for PCI vendor and device IDs fr


From: Blue Swirl
Subject: Re: [Qemu-devel] [6490] Update #defines for PCI vendor and device IDs from OpenBIOS and Linux
Date: Sun, 1 Feb 2009 17:42:56 +0200

On 2/1/09, Stuart Brady <address@hidden> wrote:
> On Sun, Feb 01, 2009 at 04:39:55PM +0200, Blue Swirl wrote:
>  > On 2/1/09, Stuart Brady <address@hidden> wrote:
>
> > > Isn't the DEC 21154 is a Tulip-compatible NIC, and not a PCI bridge?
>  >
>
> > I'd rather guess it's a PCI bridge.
>
>
> Seems I got a bit mixed up, there!
>
>
>  > > > +#define PCI_DEVICE_ID_REALTEK_RTL8029    0x8029
>  > > >  #define PCI_DEVICE_ID_REALTEK_8139       0x8139
>  > >
>
> > > (Also, RTL8029 vs. 8139?...)
>  >
>  > That's what ne2k uses (not 8139).
>
>
> Sorry, I wasn't clear -- I was just pointing at the naming i.e. RTL8029
>  as opposed to just 8029, but wasn't trying to make a big deal out of it.
>
>
>  > > I gather 0x1234/0x1111 was originally chosen by Bochs.  Unfortunately,
>  > > it is apparently allocated to 'Technical Corp.'  Would it be possible
>  > > to use something less confusing instead?
>  >
>  > The IDs could be replaced with some real, original VGA compatible PCI
>  > card, without any extra features. Bochs extensions should probably be
>  > disabled then. Any suggestions?
>
>
> Not sure... perhaps Gerd could help, here? :)
>
>  (BTW, I notice that OpenBIOS/PPC depends on this particular ID, and I
>  wonder if Bochs BIOS would have to be updated, too.)

Of course some coordinated changed would be required, if we even want to do it.

At least here is one check:
http://bochs.sourceforge.net/cgi-bin/lxr/source/bios/rombios32.c#L700




reply via email to

[Prev in Thread] Current Thread [Next in Thread]