From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34992) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eFG1D-0004Ek-2O for qemu-devel@nongnu.org; Thu, 16 Nov 2017 03:59:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eFG19-0000TE-VA for qemu-devel@nongnu.org; Thu, 16 Nov 2017 03:59:31 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52058) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eFG19-0000K8-MO for qemu-devel@nongnu.org; Thu, 16 Nov 2017 03:59:27 -0500 References: <20171106203520.7880-1-michael.nawrocki@gtri.gatech.edu> <20171106203520.7880-3-michael.nawrocki@gtri.gatech.edu> <7bb60d60-28d4-3c37-2740-fd16d7c6856a@gtri.gatech.edu> <2e6d4835-e277-fd46-12bc-612c7e57a6f4@weilnetz.de> From: Jason Wang Message-ID: <2462ccd8-176c-16d3-d995-7a90c0feea23@redhat.com> Date: Thu, 16 Nov 2017 16:59:15 +0800 MIME-Version: 1.0 In-Reply-To: <2e6d4835-e277-fd46-12bc-612c7e57a6f4@weilnetz.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v2 2/2] Add new PCI ID for i82559a List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil , Michael Nawrocki , qemu-devel@nongnu.org Cc: marcel@redhat.com, Peter Maydell , mst@redhat.com On 2017=E5=B9=B411=E6=9C=8816=E6=97=A5 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/modul= es/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 al= l > 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