From: Gerd Hoffmann <kraxel@redhat.com>
To: Stuart Brady <sdbrady@ntlworld.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6490] Update #defines for PCI vendor and device IDs from OpenBIOS and Linux
Date: Mon, 02 Feb 2009 11:23:22 +0100 [thread overview]
Message-ID: <4986C99A.3080406@redhat.com> (raw)
In-Reply-To: <20090201151617.GA14073@miranda.arrow>
>>>> +#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.
REALTEK_RTL is somewhat redundant, I'd drop the RTL from the 8029 ...
>>> 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?
Well, you probably have a hard time to find a real VGA card *with* PCI
and *without* extra features.
> Not sure... perhaps Gerd could help, here? :)
I can talk to our PCI guy, shouldn't be a big issue to get an ID for the
qemu std vga. Thats certainly better that some random ID grabbed.
cheers,
Gerd
prev parent reply other threads:[~2009-02-02 10:23 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
2009-02-01 18:03 ` Volker Ruppert
2009-02-02 10:23 ` Gerd Hoffmann [this message]
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=4986C99A.3080406@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sdbrady@ntlworld.com \
/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).