qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Stefan Weil <sw@weilnetz.de>,
	Michael Nawrocki <michael.nawrocki@gtri.gatech.edu>,
	qemu-devel@nongnu.org
Cc: marcel@redhat.com, Peter Maydell <peter.maydell@linaro.org>,
	mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/2] Add new PCI ID for i82559a
Date: Thu, 16 Nov 2017 16:59:15 +0800	[thread overview]
Message-ID: <2462ccd8-176c-16d3-d995-7a90c0feea23@redhat.com> (raw)
In-Reply-To: <2e6d4835-e277-fd46-12bc-612c7e57a6f4@weilnetz.de>



On 2017年11月16日 14:40, Stefan Weil wrote:
> Am 15.11.2017 um 14:09 schrieb Michael Nawrocki:
>> Hi Stefan,
>>
>> I've got a VxWorks driver binary that explicitly looks for device ID
>> 0x1030 (which is admittedly not ideal). It seems like the "82559
>> InBusiness 10/100" hardware uses this, though I've had trouble finding
>> an official source. The following documents reference that ID:
>>
>> https://pci-ids.ucw.cz/read/PC/8086/1030
>> http://ks.pams.ncsu.edu/pub/ncsuscyld/i386/misc/src/trees/hdstg2/modules/pcitable
>>
>> https://cateee.net/lkddb/web-lkddb/E100.html
>>
>> And I found a similar post on a different mailing list that might shed
>> some light:
>> http://www.beowulf.org/pipermail/eepro100/2000-January/000760.html
>>
>> It looks like the 8255x series of devices have a number of potential
>> IDs; maybe a property to set a specific PCI device ID would work?
>>
>> Thanks,
>> Mike
> Yes, that might be a very general solution which could be applied to all
> PCI devices.
> It could even be extended to include the vendor ID or any PCI
> configuration value
> as well.
>
> Nevertheless the technically correct solution would be a full emulation
> of the
> EEPROM. Then we could provide an EEPROM for the 82559 InBusiness 10/100",
> and the data from that EEPROM would set the right PCI device ID.
>
> Jason, until we get a better solution, the last commit should be
> reverted before
> the new QEMU version is made. That commit also added a wrong help text.
>
> Regards
> Stefan

Let me post a patch soon.

Thanks

      reply	other threads:[~2017-11-16  8:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 20:35 [Qemu-devel] [PATCH v2 0/2] Fix eepro100 simple transmission, add i82559 PCI ID Mike Nawrocki
2017-11-06 20:35 ` [Qemu-devel] [PATCH v2 1/2] Fix eepro100 simple transmission mode Mike Nawrocki
2017-11-16 16:59   ` Thomas Huth
2017-11-16 17:43     ` Thomas Huth
2017-11-16 18:09       ` Michael Nawrocki
2017-11-06 20:35 ` [Qemu-devel] [PATCH v2 2/2] Add new PCI ID for i82559a Mike Nawrocki
2017-11-07 16:12   ` Michael S. Tsirkin
2017-11-07 18:25     ` Michael Nawrocki
2017-11-14 21:41   ` Stefan Weil
2017-11-15 11:20     ` Jason Wang
2017-11-15 13:09     ` Michael Nawrocki
2017-11-16  2:33       ` Jason Wang
2017-11-16  6:40       ` Stefan Weil
2017-11-16  8:59         ` Jason Wang [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=2462ccd8-176c-16d3-d995-7a90c0feea23@redhat.com \
    --to=jasowang@redhat.com \
    --cc=marcel@redhat.com \
    --cc=michael.nawrocki@gtri.gatech.edu \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).