From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33997 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OmZyY-0000yq-Cf for qemu-devel@nongnu.org; Fri, 20 Aug 2010 18:22:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OmZyW-0000zn-2P for qemu-devel@nongnu.org; Fri, 20 Aug 2010 18:22:14 -0400 Received: from smtp.mailix.net ([66.11.225.183]:10317) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OmZyV-0000zg-K9 for qemu-devel@nongnu.org; Fri, 20 Aug 2010 18:22:12 -0400 From: "Adnan Khaleel" Subject: =?iso-8859-1?Q?Re=3A_=5BQemu-devel=5D_Template_for_developing_a_Qe?= =?iso-8859-1?Q?mu_device_with=09PCIe=3Fand_MSI-X?= In-Reply-To: 20100820052203.GD31720@valinux.co.jp Message-ID: <20100820222208.19c41df1@shadowfax.no-ip.com> Date: Fri, 20 Aug 2010 17:22:08 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-----------c9f8c5ecbe18c4949b5f09fb51eece1c" Reply-To: adnan@khaleel.us List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Isaku Yamahata This is a multi-part message in MIME format. -------------c9f8c5ecbe18c4949b5f09fb51eece1c Content-Type: multipart/alternative; boundary="-----------251619693ab541d76724c9cd48bea539" -------------251619693ab541d76724c9cd48bea539 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable After messing around with bcc, as86 and ld86 I finally got the vgabios t= o compile. Everything works as it should I'm guessing. I've attached the output fro= m lspci from the guest. I'll spend sometime looking at the device models= and see how I can implement a model of what I'm interested in. Is the overall architecture of any qemu device still similar to how a ty= pical qemu pci device is or is there anything I should be aware of=3F Thanks again Isaku. AK =5F=5F=5F=5F=5F =20 From: Isaku Yamahata [mailto:yamahata@valinux.co.jp] To: Adnan Khaleel [mailto:adnan@khaleel.us] Cc: qemu-devel@nongnu.org Sent: Fri, 20 Aug 2010 00:22:03 -0500 Subject: Re: [Qemu-devel] Template for developing a Qemu device with PCI= e=3Fand MSI-X On Thu, Aug 19, 2010 at 01:32:42PM -0500, Adnan Khaleel wrote: > Isaku, >=20 > I'm having some difficulties building the sources, I get the followi= ng message >=20 > *akhaleel@yar95 qemu-q35 $ ./configure --help > : bad interpreter: No such file or directory >=20 > And I get a similar error while compiling seabios as well. > > What shell are you using or am I missing something=3F I'm compiling = from a > typical bash shell and using gcc v4.4.0. =20 I'm not sure. configure script isn't modified. Can you compile normal qemu=3F The first line of the script is #!/bin/sh. I suppose you have /bin/sh. =20 =20 > In vgabios, there is a requirement for bcc. Is that borland C compil= er=3F =20 No. Most Linux destro has bcc package. Just you need to install it lik= e yum install bcc or something. =20 Thanks, =20 =20 >=20 > Thanks >=20 > Adnan >=20 > =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81= =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81= =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81= =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81= =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81 > From: Isaku Yamahata [mailto:yamahata@valinux.co.jp] > To: Adnan Khaleel [mailto:adnan@khaleel.us] > Cc: qemu-devel@nongnu.org > Sent: Wed, 18 Aug 2010 22:19:04 -0500 > Subject: Re: [Qemu-devel] Template for developing a Qemu device = with PCIe > and MSI-X >=20 > On Wed, Aug 18, 2010 at 02:10:10PM -0500, Adnan Khaleel wrote: > > Hello Qemu developers, > > > > I'm interested in developing a device model that plugs into Qe= mu that is > based > > on a PCIe interface and uses MSI-X. My goal is to ultimately a= ttach a GPU > > simulator to this PCIe interface and use the entire platfom (Q= emu + GPU > > simulator) for studying cpu, gpu interactions. > > > > I'm not terribly familiar with the Qemu device model and I'm l= ooking for > some > > assistance, perhaps a starting template for pcie and msi-x tha= t would > offer the > > basic functionality that I could then build upon. > > > > I have looked at the various devices that already modelled tha= t are > included > > with Qemu (v0.12.5 at least) and I've noticed several a few pc= i devices, > eg; > > ne2k and cirrus-pci etc, however only one device truly seems t= o utilize > both > > the technologies that I'm interested in and that is the virtio= -pci.c > > > > I'm not sure what virtio-pci does so I'm not sure if that is a= suitable > > starting point for me. > > > > Any help, suggestions etc would be extremely helpful and much > appreciated. >=20 > Qemu doesn't support pcie at the moment. > Only partial patches have been merged, still more patches have t= o > be merged for pcie to fully work. The following repo is availabl= e. >=20 > git clone http://people.valinux.co.jp/~yamahata/qemu/q35/qemu > git clone http://people.valinux.co.jp/~yamahata/qemu/q35/seabios > git clone http://people.valinux.co.jp/~yamahata/qemu/q35/vgabios >=20 > Note: patched seabios and vgabios are needed, you have to pass A= CPI DSDT > for q35. > example: > qemu-system-x86=5F64 -M pc=5Fq35 -acpitable load=5Fheader,data= =3Droms/seabios/src/ > q35-acpi-dsdt.aml >=20 > This repo is for those who want to try/develop pcie support, > not for upstream merge. So they include patches unsuitable for u= pstream. > The repo includes pcie port switch emulator which utilize pcie a= nd > MSI(not MSI-X). >=20 > The difference between PCI device and PCIe device is configurati= on > space size. > By setting PCIDeviceInfo::is=5Fexpress =3D 1, you'll get 4K conf= iguration > space. Helper functions for pcie are found in qemu/hw/pcie.c > For msi-x, see qemu/hw/msix.c. >=20 > Thanks, > -- > yamahata >=20 =20 --=20 yamahata =20 -------------251619693ab541d76724c9cd48bea539 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
After messing around with bcc, as86 and= ld86 I finally got the vgabios to compile.

Everything works as i= t should I'm guessing. I've attached the output from lspci from the gues= t. I'll spend sometime looking at the device models and see how I can im= plement a model of what I'm interested in.

Is the overall archite= cture of any qemu device still similar to how a typical qemu pci device = is or is there anything I should be aware of=3F

Thanks again Isak= u.

AK
<= b>From: Isaku Yamahata [mailto:yamahata@valinux.co.jp]
To:= Adnan Khaleel [mailto:adnan@khaleel.us]
Cc: qemu-devel@nongnu= .org
Sent: Fri, 20 Aug 2010 00:22:03 -0500
Subject: = Re: [Qemu-devel] Template for developing a Qemu device with=09PCIe=3Fand= MSI-X

On Thu, Aug 19, 2010 at 01:32:42PM -0500, Adnan Khaleel wr= ote:
> Isaku,
>
> I'm having some difficulties building the sources, I get the follow= ing message
>
> *akhaleel@yar95 qemu-q35 $ ./= configure --help
> : bad interpreter: No such file or directory
>
> And I get a similar error while compiling seabios as well.
>
> What shell are you using or am I missing something=3F I'm compiling= from a
> typical bash shell and using gcc v4.4.0.

I'm not sure. configure script isn't modified.
Can you compile normal qemu=3F
The first line of the script is #!/bin/sh. I suppose you have /bin/sh.

> In vgabios, there is a requirement for bcc. Is that borland C compi= ler=3F

No. Most Linux destro has bcc package. Just you need to install it like<= br> yum install bcc or something.

Thanks,


>
> Thanks
>
> Adnan
>
> =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81= =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81= =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81= =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81= =E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81=E2=94=81
> From: Isaku Yamahata [mailto:yamahata@valinux.co.jp]
> To: Adnan Khaleel [mailto:a= dnan@khaleel.us]
> Cc: qemu-devel@nongnu.= org
> Sent: Wed, 18 Aug 2010 22:19:04 -0500
> Subject: Re: [Qemu-devel] Template for developing a Qemu device= with PCIe
> and MSI-X
>
> On Wed, Aug 18, 2010 at 02:10:10PM -0500, Adnan Khaleel wrote:<= br> > > Hello Qemu developers,
> >
> > I'm interested in developing a device model that plugs int= o Qemu that is
> based
> > on a PCIe interface and uses MSI-X. My goal is to ultimate= ly attach a GPU
> > simulator to this PCIe interface and use the entire platfo= m (Qemu + GPU
> > simulator) for studying cpu, gpu interactions.
> >
> > I'm not terribly familiar with the Qemu device model and I= 'm looking for
> some
> > assistance, perhaps a starting template for pcie and msi-x= that would
> offer the
> > basic functionality that I could then build upon.
> >
> > I have looked at the various devices that already modelled= that are
> included
> > with Qemu (v0.12.5 at least) and I've noticed several a fe= w pci devices,
> eg;
> > ne2k and cirrus-pci etc, however only one device truly see= ms to utilize
> both
> > the technologies that I'm interested in and that is the vi= rtio-pci.c
> >
> > I'm not sure what virtio-pci does so I'm not sure if that = is a suitable
> > starting point for me.
> >
> > Any help, suggestions etc would be extremely helpful and m= uch
> appreciated.
>
> Qemu doesn't support pcie at the moment.
> Only partial patches have been merged, still more patches have = to
> be merged for pcie to fully work. The following repo is availab= le.
>
> git clone http://people.valinux.co.jp/~yamahata/q= emu/q35/qemu
> git clone http://people.valinux.co.jp/~yamahat= a/qemu/q35/seabios
> git clone http://people.valinux.co.jp/~yamahat= a/qemu/q35/vgabios
>
> Note: patched seabios and vgabios are needed, you have to pass = ACPI DSDT
> for q35.
> example:
> qemu-system-x86=5F64 -M pc=5Fq35 -acpitable load=5Fheader,data= =3Droms/seabios/src/
> q35-acpi-dsdt.aml
>
> This repo is for those who want to try/develop pcie support, > not for upstream merge. So they include patches unsuitable for = upstream.
> The repo includes pcie port switch emulator which utilize pcie = and
> MSI(not MSI-X).
>
> The difference between PCI device and PCIe device is configurat= ion
> space size.
> By setting PCIDeviceInfo::is=5Fexpress =3D 1, you'll get 4K con= figuration
> space. Helper functions for pcie are found in qemu/hw/pcie.c > For msi-x, see qemu/hw/msix.c.
>
> Thanks,
> --
> yamahata
>

--
yamahata
-------------251619693ab541d76724c9cd48bea539-- -------------c9f8c5ecbe18c4949b5f09fb51eece1c Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="pci.txt" 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Co= ntroller 00:01.0 VGA compatible controller: Cirrus Logic GD 5446 00:04.0 PCI bridge: Intel Corporation X58 I/O Hub PCI Express Root Port = 0 (rev 02) 00:18.0 PCI bridge: Intel Corporation X58 I/O Hub PCI Express Root Port = 0 (rev 02) 00:18.1 PCI bridge: Intel Corporation X58 I/O Hub PCI Express Root Port = 0 (rev 02) 00:18.2 PCI bridge: Intel Corporation X58 I/O Hub PCI Express Root Port = 0 (rev 02) 00:18.3 PCI bridge: Intel Corporation X58 I/O Hub PCI Express Root Port = 0 (rev 02) 00:18.4 PCI bridge: Intel Corporation X58 I/O Hub PCI Express Root Port = 0 (rev 02) 00:18.5 PCI bridge: Intel Corporation X58 I/O Hub PCI Express Root Port = 0 (rev 02) 00:19.0 PCI bridge: Intel Corporation X58 I/O Hub PCI Express Root Port = 0 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Contr= oller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (= rev 02) 36:00.0 PCI bridge: Texas Instruments Device 8232 (rev 02) 36:00.1 PCI bridge: Texas Instruments Device 8232 (rev 02) 36:00.2 PCI bridge: Texas Instruments Device 8232 (rev 02) 36:00.3 PCI bridge: Texas Instruments Device 8232 (rev 02) 36:00.4 PCI bridge: Texas Instruments Device 8232 (rev 02) 36:00.5 PCI bridge: Texas Instruments Device 8232 (rev 02) 36:00.6 PCI bridge: Texas Instruments Device 8232 (rev 02) 36:00.7 PCI bridge: Texas Instruments Device 8232 (rev 02) 37:00.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:01.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:02.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:03.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:04.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:05.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:06.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:07.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:08.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:09.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:0a.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:0b.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:0c.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:0d.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:0e.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 37:0f.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:00.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:01.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:02.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:03.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:04.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:05.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:06.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:07.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:08.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:09.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:0a.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:0b.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:0c.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:0d.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:0e.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 48:0f.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:00.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:01.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:02.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:03.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:04.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:05.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:06.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:07.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:08.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:09.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:0a.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:0b.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:0c.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:0d.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:0e.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 59:0f.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:00.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:01.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:02.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:03.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:04.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:05.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:06.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:07.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:08.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:09.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:0a.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:0b.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:0c.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:0d.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:0e.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 6a:0f.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:00.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:01.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:02.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:03.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:04.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:05.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:06.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:07.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:08.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:09.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:0a.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:0b.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:0c.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:0d.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:0e.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 7b:0f.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:00.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:01.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:02.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:03.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:04.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:05.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:06.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:07.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:08.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:09.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:0a.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:0b.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:0c.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:0d.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:0e.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 8c:0f.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:00.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:01.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:02.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:03.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:04.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:05.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:06.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:07.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:08.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:09.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:0a.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:0b.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:0c.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:0d.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:0e.0 PCI bridge: Texas Instruments Device 8233 (rev 01) 9d:0f.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:00.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:01.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:02.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:03.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:04.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:05.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:06.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:07.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:08.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:09.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:0a.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:0b.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:0c.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:0d.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:0e.0 PCI bridge: Texas Instruments Device 8233 (rev 01) ae:0f.0 PCI bridge: Texas Instruments Device 8233 (rev 01) c0:00.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet = Controller (rev 03) c0:01.0 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Trito= n II] c0:1c.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 05) c0:1d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 05) c0:1e.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 05) c0:1f.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 05) -------------c9f8c5ecbe18c4949b5f09fb51eece1c--