I recently was reminded of LinuxBIOS by that /. article, and remembered how I thought it rocked back in v1 days, when I was a penniless student. Now I have a job, which equals paychecks, and more free time. I'd love to be able to contribute something to the project.
Unfortunately, I'm a sysadmin, not a programmer, and barring snippets of perl to automate system tasks, I can't code for toffee. :-(
Guess I'll just have to buy some hardware and be a testing monkey then :-)
At the moment at work we have a Via PD10000, which we use for a bunch of quite mission-critical things. We can reboot it as often as we like, but at the moment, doing so is a PITA because it takes so long. Hmm. Wouldn't it be nice if I could boot LinuxBIOS on it...
So here I am, bidding on another one on eBay, so that we can have a spare in case our mission-crit one dies. But it would be a shame for the spare to sit around doing nothing...
Its worth saying at this point that I don't want to divert anyone coding actually /useful/ things, so if I have to wait around for someone to have a spare moment to give me a hand, thats fine.
I'm happy to go get a chip puller, some spare bios chips, a chip programmer, etc. Just tell me where to get the right ones.
If anyone wants to tell me I'm not going to do much good, that's okay. I'm buying the board as a spare anyway. If I can do some good by helping get it working under LinuxBIOS, well then that's great and where do I start...
So, my question is this: Shall I go and get a POST card, a chip flasher and some spare lumps of silicon, or should I not bother?
Here's hoping I can make a contribution,
Dave, Sysadmin, Senokian Solutions
* Richard Wilson Richard.Wilson@senokian.com [070312 13:06]:
Guess I'll just have to buy some hardware and be a testing monkey then :-)
At the moment at work we have a Via PD10000, which we use for a bunch of quite mission-critical things. We can reboot it as often as we like, but at the moment, doing so is a PITA because it takes so long. Hmm. Wouldn't it be nice if I could boot LinuxBIOS on it...
Can you please send an lspci -vv to this list?
So here I am, bidding on another one on eBay, so that we can have a spare in case our mission-crit one dies. But it would be a shame for the spare to sit around doing nothing...
Heh.. given that it works (depends on the lspci), you might put it into the LinuxBIOS test system:
http://www.linuxbios.org/Distributed_and_Automated_Testsystem
We started the system last year, but only a single board has been put to test since then.
Its worth saying at this point that I don't want to divert anyone coding actually /useful/ things, so if I have to wait around for someone to have a spare moment to give me a hand, thats fine.
Just send your questions to the list. There's almost always something who might answer them.
I'm happy to go get a chip puller, some spare bios chips, a chip programmer, etc. Just tell me where to get the right ones.
I bought this programmer, and I think it is a really good deal: http://www.progshop.com/shop/programmer/galep/galep4.shtml it burns about everything, requires a non-usb parport though
for the beginning you might get away cheaper with a bios savior (if you still get one) or with hotswapping the chips.
So, my question is this: Shall I go and get a POST card, a chip flasher and some spare lumps of silicon, or should I not bother?
POST card is not required. Better get a serial null modem cable. That's a lot more convenient for debugging.
On Mon, Mar 12, 2007 at 02:15:58PM +0100, Stefan Reinauer wrote:
I bought this programmer, and I think it is a really good deal: http://www.progshop.com/shop/programmer/galep/galep4.shtml it burns about everything, requires a non-usb parport though
What's the software situation Stefan? Free software support? Do you know of any programmers that are supported by free software?
Thanks, Ward.
* Ward Vandewege ward@gnu.org [070312 14:21]:
On Mon, Mar 12, 2007 at 02:15:58PM +0100, Stefan Reinauer wrote:
I bought this programmer, and I think it is a really good deal: http://www.progshop.com/shop/programmer/galep/galep4.shtml it burns about everything, requires a non-usb parport though
What's the software situation Stefan? Free software support? Do you know of any programmers that are supported by free software?
Don't think any of them do, sorry :-(
I think the artec group LPC dongle comes with open source software, but that is a different model.
Some people on this list were talking about creating an open alternative to the bios savior, with more or less intelligence. (including Peter and me), but it did not work out yet.
Ironwood Electronics sells a "PLCC clip on base", an inverted PLCC socket that can be plugged on a soldered-in flash part. Together with a BIOS savior kind of device, this would be a really cool thing.
Though I want to get my hands on a device I can use with the artec group LPC dongle. It has cool features, such as "console by rom write". You write some sequence to the flash chip/dongle and get a console on the other (USB) end... Pretty good stuff for a 150$ (no guarantee) device..
Stefan
On Mon, Mar 12, 2007 at 02:45:05PM +0100, Stefan Reinauer wrote:
- Ward Vandewege ward@gnu.org [070312 14:21]:
On Mon, Mar 12, 2007 at 02:15:58PM +0100, Stefan Reinauer wrote:
I bought this programmer, and I think it is a really good deal: http://www.progshop.com/shop/programmer/galep/galep4.shtml it burns about everything, requires a non-usb parport though
What's the software situation Stefan? Free software support? Do you know of any programmers that are supported by free software?
Don't think any of them do, sorry :-(
I think the artec group LPC dongle comes with open source software, but that is a different model.
I assume you're referring to this
http://www.artecgroup.com/products/hardware-products/programmable-lpc-dongle...
Python code, usb device - I like this. It says it comes with an 'LPC cable'; any idea what that looks like? Presumably some sort of plcc adapter would still be required?
Some people on this list were talking about creating an open alternative to the bios savior, with more or less intelligence. (including Peter and me), but it did not work out yet.
Yeah, I remember that discussion. I do hope something comes out of that.
Richard Smith mentioned this ROM emulator to me:
http://www.tech-tools.com/er3.htm
The dos-based cli tools work under wine, he says. That's better than nothing, but still proprietary software of course, so not an option for the FSF.
Ironwood Electronics sells a "PLCC clip on base", an inverted PLCC socket that can be plugged on a soldered-in flash part. Together with a BIOS savior kind of device, this would be a really cool thing.
Oh! That's very interesting. So if you'd clip this onto an smd-soldered plcc chip (like on the m57sli-s4), and plug in a bios savior, would the bios savior allow you to switch between the on-board chip and the built-in bios savior chip?
Though I want to get my hands on a device I can use with the artec group LPC dongle. It has cool features, such as "console by rom write". You write some sequence to the flash chip/dongle and get a console on the other (USB) end... Pretty good stuff for a 150$ (no guarantee) device..
That's not a bad price at all!
Thanks, Ward.
* Ward Vandewege ward@gnu.org [070312 16:02]:
I assume you're referring to this
http://www.artecgroup.com/products/hardware-products/programmable-lpc-dongle...
Yes, that's it.
Python code, usb device - I like this. It says it comes with an 'LPC cable'; any idea what that looks like? Presumably some sort of plcc adapter would still be required?
It is a 10pin (or so) header on the mainboard, similar to an IDE connector, just a lot less pins.
It would be interesting to try plug a plcc clip base or some such to it. no idea whether that is possible.
Ironwood Electronics sells a "PLCC clip on base", an inverted PLCC socket that can be plugged on a soldered-in flash part. Together with a BIOS savior kind of device, this would be a really cool thing.
Oh! That's very interesting. So if you'd clip this onto an smd-soldered plcc chip (like on the m57sli-s4), and plug in a bios savior, would the bios savior allow you to switch between the on-board chip and the built-in bios savior chip?
I don't think so, because you need to switch the chip select pin. So you would at least have to cut one pin and solder it to your logic.
But maybe a cable to connect a soldered flash chip to a flash burner would be possible? Then such a board could be revived with a GalepIV or a Willem.
It's just ideas, though. No idea what can be done and what will fail. Hardware is more tricky than it looks at the first glimpse sometimes.
On Mon, Mar 12, 2007 at 04:38:12PM +0100, Stefan Reinauer wrote:
Python code, usb device - I like this.
You can also get the VHDL for the FPGA from opencores.org.
This is the first "open hardware" product I've come across.
It says it comes with an 'LPC cable'; any idea what that looks like? Presumably some sort of plcc adapter would still be required?
It is a 10pin (or so) header on the mainboard, similar to an IDE connector, just a lot less pins.
It would be interesting to try plug a plcc clip base or some such to it. no idea whether that is possible.
Sure, but it will need an adapter of course. (Just cables really.)
One thing to note is that the cables need to be very short (no longer than some few centimeters says Artec) because of the signalling speed.
//Peter
* Peter Stuge stuge-linuxbios@cdy.org [070313 07:57]:
One thing to note is that the cables need to be very short (no longer than some few centimeters says Artec) because of the signalling speed.
Interesting. And people always complain flash would be slow :)
On Tue, Mar 13, 2007 at 10:15:24AM +0100, Stefan Reinauer wrote:
- Peter Stuge stuge-linuxbios@cdy.org [070313 07:57]:
One thing to note is that the cables need to be very short (no longer than some few centimeters says Artec) because of the signalling speed.
Interesting. And people always complain flash would be slow :)
The LPC clock can/will run at 33MHz. The number of clocks required per byte is another matter.
//Peter
Stefan Reinauer wrote:
- Richard Wilson Richard.Wilson@senokian.com [070312 13:06]:
Guess I'll just have to buy some hardware and be a testing monkey then :-)
At the moment at work we have a Via PD10000, which we use for a bunch of quite mission-critical things. We can reboot it as often as we like, but at the moment, doing so is a PITA because it takes so long. Hmm. Wouldn't it be nice if I could boot LinuxBIOS on it...
Can you please send an lspci -vv to this list?
The following was made from the lspci in the *pciutils-2.2.1 package from OpenBSD 4.0 with openbsd -vv. It is included as an attatchment for those who find it easier. http://www.openbsd.org/4.0_packages/i386/pciutils-2.2.1.tgz-long.html
(In case anyone's interested, it boots off a 512M flash card on a CF to IDE converter)
00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- Latency: 8 Region 0: Memory at e6000000 (32-bit, prefetchable) Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x4 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+ Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e4000000-e5ffffff Prefetchable memory behind bridge: e0000000-e3ffffff Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR+ BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0f.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 8b) Subsystem: VIA Technologies, Inc. Unknown device 0106 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (750ns min, 2000ns max), Cache Line Size 08 Interrupt: pin A routed to IRQ 12 Region 0: I/O ports at d000 Region 1: Memory at e7000000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size 08 Interrupt: pin A routed to IRQ 11 Region 4: I/O ports at d400 Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size 08 Interrupt: pin B routed to IRQ 11 Region 4: I/O ports at d800 Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size 08 Interrupt: pin C routed to IRQ 9 Region 4: I/O ports at dc00 Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size 08 Interrupt: pin D routed to IRQ 12 Region 0: Memory at e7001000 (32-bit, non-prefetchable) Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 Interrupt: pin A routed to IRQ 255 Region 4: I/O ports at e000 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin C routed to IRQ 9 Region 0: I/O ports at e400 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (750ns min, 2000ns max), Cache Line Size 08 Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at e800 Region 1: Memory at e7002000 (32-bit, non-prefetchable) Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03) (prog-if 00 [VGA]) Subsystem: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (500ns min) Interrupt: pin A routed to IRQ 11 Region 0: Memory at e0000000 (32-bit, prefetchable) Region 1: Memory at e4000000 (32-bit, non-prefetchable) Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [70] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
*
00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- Latency: 8 Region 0: Memory at e6000000 (32-bit, prefetchable) Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x4 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+ Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e4000000-e5ffffff Prefetchable memory behind bridge: e0000000-e3ffffff Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR+ BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0f.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 8b) Subsystem: VIA Technologies, Inc. Unknown device 0106 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (750ns min, 2000ns max), Cache Line Size 08 Interrupt: pin A routed to IRQ 12 Region 0: I/O ports at d000 Region 1: Memory at e7000000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size 08 Interrupt: pin A routed to IRQ 11 Region 4: I/O ports at d400 Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size 08 Interrupt: pin B routed to IRQ 11 Region 4: I/O ports at d800 Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size 08 Interrupt: pin C routed to IRQ 9 Region 4: I/O ports at dc00 Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size 08 Interrupt: pin D routed to IRQ 12 Region 0: Memory at e7001000 (32-bit, non-prefetchable) Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 Interrupt: pin A routed to IRQ 255 Region 4: I/O ports at e000 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) Subsystem: VIA Technologies, Inc. Unknown device aa01 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin C routed to IRQ 9 Region 0: I/O ports at e400 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (750ns min, 2000ns max), Cache Line Size 08 Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at e800 Region 1: Memory at e7002000 (32-bit, non-prefetchable) Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03) (prog-if 00 [VGA]) Subsystem: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (500ns min) Interrupt: pin A routed to IRQ 11 Region 0: Memory at e0000000 (32-bit, prefetchable) Region 1: Memory at e4000000 (32-bit, non-prefetchable) Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [70] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
* Richard Wilson Richard.Wilson@senokian.com [070312 15:37]:
The following was made from the lspci in the *pciutils-2.2.1 package from OpenBSD 4.0 with openbsd -vv. It is included as an attatchment for those who find it easier. http://www.openbsd.org/4.0_packages/i386/pciutils-2.2.1.tgz-long.html
(In case anyone's interested, it boots off a 512M flash card on a CF to IDE converter)
00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
This looks good. Definitely worth a try, using the via/epia-m target.
-
Peter Stuge -
Quux -
Richard Wilson -
Stefan Reinauer -
Ward Vandewege