From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
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 [thread overview]
Message-ID: <f43fc5580902010742n95a7321j592d74940eae6a32@mail.gmail.com> (raw)
In-Reply-To: <20090201151617.GA14073@miranda.arrow>
On 2/1/09, Stuart Brady <sdbrady@ntlworld.com> wrote:
> On Sun, Feb 01, 2009 at 04:39:55PM +0200, Blue Swirl wrote:
> > On 2/1/09, Stuart Brady <sdbrady@ntlworld.com> 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
next prev parent reply other threads:[~2009-02-01 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 12:01 [Qemu-devel] [6490] Update #defines for PCI vendor and device IDs from OpenBIOS and Linux Blue Swirl
2009-02-01 13:22 ` Stuart Brady
2009-02-01 14:39 ` Blue Swirl
2009-02-01 15:16 ` Stuart Brady
2009-02-01 15:42 ` Blue Swirl [this message]
2009-02-01 18:03 ` Volker Ruppert
2009-02-02 10:23 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580902010742n95a7321j592d74940eae6a32@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).