Hi, I'm new to LB, and after studying the list archives for the past week, I've started working on getting LB installed on yet another Geode GX1 board. This system is actually a MaxSpeed MaxTerm 230, an old thin client system that had been surplussed. The board inside was manufactured by DTRI (www.dtresearch.com), and is model WBTG v1.1. The WBTG has a 300Mhz GX1, 64MB of on-board DRAM, and 8MB of on-board flash. It uses the CS5530 southbridge, an NS PC97317 SuperIO, and an NS 83815 10/100 Ethernet.
Since the CPU, southbridge, and SuperIO are the same as the Eaglelion 5bcm, I have started with that target. And my initial LB image, complete with FILO, basically works! At least, it passes the smoke test.
Questions/issues thus far: 1) IRQ questions. I got the error about copying the IRQ table, and I know I can fix this by using an uncompressed image. But that leaves me with a few questions: a) Does using an uncompressed LB image preclude having a failsafe image, due to uncompressed image size? Not a problem for me, just curious. b) How can I create an IRQ map for this system, or do I not worry about it? This machine was built to only run WinCE, so I can't take the stock BIOS, boot Linux, and do any investigating.
2) When initializing the IDE on the CS5530, LB reports "missing enable_resources", even though a few lines prior, it looks like it assigns the proper I/O range for IDE. What does this mean? (See attached LB output.)
3) I have several uses in mind for these boards, if I can get more of them. Some uses would involve using the audio and VGA, both of which I know are problematic. I think the VGA part I can do, but what about audio? Is "VSA" required to initialize the audio? I guess what I'm wondering is, what's the minimum LB has to do before Linux can see (and use) the audio. FWIW, this board has an NS LM4548 audio chip, which I assume is a support chip for the XpressAudio? Or better, maybe DTRI decided to scrap XpressAudio and this chip is standalone... that would make me happy. :-)
Thanks to everyone on the LB team, it's clear from the archives that you all are really dedicated. And thanks to Hamish for the GX1 work in LBv2.
-Jonathan
LinuxBIOS-1.1.8.0Normal Fri Apr 21 04:23:44 EDT 2006 starting... Setting up default parameters for memory Sizing memory Probing for DIMM0 Probing for DIMM1 Found DIMM1 Page Size: 00001000 Component Banks: 4 Module Banks: 1 DIMM size: 04000000 MC_BANK_CFG = 14200070 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.8.0Normal Fri Apr 21 04:23:44 EDT 2006 booting... clocks_per_usec: 449 Enumerating buses... Finding PCI configuration type. PCI: Using configuration type 1 PCI_DOMAIN: 0000 enabled PCI: pci_scan_bus for bus 0 PCI: 00:00.0 [1078/0001] enabled PCI: 00:12.0 [1078/0100] enabled PCI: 00:12.1 [1078/0101] enabled PCI: 00:12.2 [1078/0102] enabled PCI: 00:12.3 [1078/0103] enabled PCI: 00:12.4 [1078/0104] enabled PCI: 00:13.0 [0e11/a0f8] enabled PCI: 00:15.0 [100b/0020] enabled PNP: 002e.0 enabled PNP: 002e.1 enabled PNP: 002e.2 enabled PNP: 002e.3 disabled PNP: 002e.4 enabled PNP: 002e.5 enabled PNP: 002e.6 enabled PNP: 002e.7 enabled PNP: 002e.8 enabled PCI: 00:12.1 disabled PCI: 00:12.2 enabled PCI: 00:12.3 disabled PCI: 00:12.4 disabled PCI: pci_scan_bus returning with max=00 done Allocating resources... Reading resources... Done reading resources. Setting resources... BC_DRAM_TOP = 0x03bfffff MC_GBASE_ADD = 0x00000078 I would set ram size to 60 Mbytes PCI: 00:12.1 10 <- [0x00febf3000 - 0x00febf30ff] mem PCI: 00:12.2 20 <- [0x0000001400 - 0x000000147f] io PCI: 00:12.3 10 <- [0x00febf4000 - 0x00febf407f] mem PCI: 00:12.4 10 <- [0x00febf0000 - 0x00febf0fff] mem PCI: 00:13.0 10 <- [0x00febf1000 - 0x00febf1fff] mem PCI: 00:15.0 10 <- [0x0000001000 - 0x00000010ff] io PCI: 00:15.0 14 <- [0x00febf2000 - 0x00febf2fff] mem PCI: 00:15.0 30 <- [0x00febe0000 - 0x00febeffff] romem Done setting resources. Done allocating resources. Enabling resources... PCI: 00:00.0 cmd <- 147 PCI: 00:12.0 cmd <- 14f PCI: 00:12.2 missing enable_resources PCI: 00:12.1 cmd <- 142 PCI: 00:12.2 cmd <- 141 PCI: 00:12.3 cmd <- 142 PCI: 00:12.4 cmd <- 142 PCI: 00:13.0 cmd <- 142 PCI: 00:15.0 cmd <- 143 done. Initializing devices... Root Device init PCI: 00:00.0 init northbridge: northbridge_init() PCI: 00:12.0 init PNP: 002e.0 init PNP: 002e.1 init PNP: 002e.2 init PNP: 002e.4 init PNP: 002e.5 init PNP: 002e.6 init PNP: 002e.7 init PNP: 002e.8 init PCI: 00:12.1 init PCI: 00:12.2 init PCI: 00:12.3 init PCI: 00:12.4 init PCI: 00:13.0 init PCI: 00:15.0 init Devices initialized Copying IRQ routing tables to 0xf0000...done. Verifing copy of IRQ routing tables at 0xf0000...failed Moving GDT to 0x500...ok Wrote linuxbios table at: 00000530 - 000006b0 checksum c9bc
Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3
33:stream_init() - rom_stream: 0xfffc0000 - 0xfffcffff Found ELF candiate at offset 0 New segment addr 0x100000 size 0x23600 offset 0xc0 filesize 0x9568 (cleaned up) New segment addr 0x100000 size 0x23600 offset 0xc0 filesize 0x9568 New segment addr 0x123600 size 0x48 offset 0x9640 filesize 0x48 (cleaned up) New segment addr 0x123600 size 0x48 offset 0x9640 filesize 0x48 Dropping non PT_LOAD segment Dropping non PT_LOAD segment Loading Segment: addr: 0x0000000000100000 memsz: 0x0000000000023600 filesz: 0x00 00000000009568 Clearing Segment: addr: 0x0000000000109568 memsz: 0x000000000001a098 Loading Segment: addr: 0x0000000000123600 memsz: 0x0000000000000048 filesz: 0x00 00000000000048 Jumping to boot code at 0x107684 FILO version 0.4.2 (root@fc4-dev) Fri Apr 21 04:11:43 EDT 2006 Press <Enter> for default boot, or <Esc> for boot prompt... timed out boot: hda1:/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200 IDE time out No drive detected on IDE channel 0 boot: hda1:/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200
Questions/issues thus far:
- IRQ questions. I got the error about copying the IRQ table, and I
know I can fix this by using an uncompressed image. But that leaves me with a few questions:
After enabling read/write/cache for BC_XMAP_2 and BC_XMAP_3 in gx_setup.inc under src/cpu/amd/model_gx1 the irq_table is copied and verified well.
You should set both to 0x33333333 or 0x77777777 to try this
a) Does using an uncompressed LB image preclude having a failsafe image, due to uncompressed image size? Not a problem for me, just curious. b) How can I create an IRQ map for this system, or do I not worry about it? This machine was built to only run WinCE, so I can't take the stock BIOS, boot Linux, and do any investigating.
- When initializing the IDE on the CS5530, LB reports "missing
enable_resources", even though a few lines prior, it looks like it assigns the proper I/O range for IDE. What does this mean? (See attached LB output.)
Sorry no answer for that :(
- I have several uses in mind for these boards, if I can get more of
them. Some uses would involve using the audio and VGA, both of which I know are problematic. I think the VGA part I can do, but what about
Read the allwell stb3036 threads, I run in several problems to get the vga working :D
audio? Is "VSA" required to initialize the audio? I guess what I'm wondering is, what's the minimum LB has to do before Linux can see (and use) the audio. FWIW, this board has an NS LM4548 audio chip, which I
You should set first the audio device to "on" in the Config.lb under src/mainboard/eaglelion/5bcm
I have the same NS audio companion chip on my board, but not test this yet.
assume is a support chip for the XpressAudio? Or better, maybe DTRI decided to scrap XpressAudio and this chip is standalone... that would make me happy. :-)
Sorry, but the datasheets says that the NS LM4548 is a companion for the internal cs5530 audio stuff. Therefor I think that thing is not standalone. However, Linux detects this devices as Kalhua Audio. I will test it in the next days.
chris
On Sat, May 13, 2006 at 10:04:28PM +0200, Christian Sühs wrote:
assume is a support chip for the XpressAudio? Or better, maybe DTRI
Sorry, but the datasheets says that the NS LM4548 is a companion for the internal cs5530 audio stuff. Therefor I think that thing is not standalone. However, Linux detects this devices as Kalhua Audio. I will test it in the next days.
Would be neat if it works, I have a faint memory of XpressAudio requiring the VSM in order for some driver to find it properly, but ideally Linux has learned to do what the VSM does. :)
//Peter
* Peter Stuge stuge-linuxbios@cdy.org [060514 15:15]:
On Sat, May 13, 2006 at 10:04:28PM +0200, Christian Sühs wrote:
assume is a support chip for the XpressAudio? Or better, maybe DTRI
Sorry, but the datasheets says that the NS LM4548 is a companion for the internal cs5530 audio stuff. Therefor I think that thing is not standalone. However, Linux detects this devices as Kalhua Audio. I will test it in the next days.
Would be neat if it works, I have a faint memory of XpressAudio requiring the VSM in order for some driver to find it properly, but ideally Linux has learned to do what the VSM does. :)
Does LinuxBIOS not support VSM now?
There is a native cx5530 audio driver, but it's for FreeBSD. http://63.249.85.132/gx_audio/index.html http://alumni.cse.ucsc.edu/~brucem/gx_audio/ It may just need to be ported over to linux if it hasn't been already.
Also, the latest kernels no longer use durango in the framebuffer driver. It may be possible to port it to linuxbios and dispense with VGA and even VSA altogether, which I think has been the goal for a long time.
Bryan
AMD provides an OSS audio driver patch for 2.4.x kernels, so I think that will suit my immediate needs. So I think that just means LB has to know how to initialize the XpressAudio and assign resources to it. I don't know how much, if any, VSA "stuff" is required to do this... hopefully not much.
-Jonathan
Bryan E. Chafy wrote:
There is a native cx5530 audio driver, but it's for FreeBSD. http://63.249.85.132/gx_audio/index.html http://alumni.cse.ucsc.edu/~brucem/gx_audio/ It may just need to be ported over to linux if it hasn't been already.
Also, the latest kernels no longer use durango in the framebuffer driver. It may be possible to port it to linuxbios and dispense with VGA and even VSA altogether, which I think has been the goal for a long time.
On Sun, May 14, 2006 at 12:14:22PM -0400, Jonathan Sturges wrote:
AMD provides an OSS audio driver patch for 2.4.x kernels, so I think that will suit my immediate needs.
The OSS driver could require a VSM.. Yes, I think LB does VSA now thanks to Ollie, but I still consider VSA a hack. :p
Excellent news about scrapping durango, that was certainly a "remarkable" piece of code. (100kb kernel module interfacing with the graphics hardware..)
The FBSD audio driver looks great!
//Peter
Peter Stuge schrieb:
On Sun, May 14, 2006 at 12:14:22PM -0400, Jonathan Sturges wrote:
AMD provides an OSS audio driver patch for 2.4.x kernels, so I think that will suit my immediate needs.
I'm not sure, but in the past I was able to use simple audio functions with kernel 2.4.22 and ALSA or OSS.
I think it was the great sb or sb16 modul in standard configuration under factory bios. without special drivers for the cs5530.
However, I was able to hear mp3 on that board.
Currently I played around with newer ALSA driver and kernel 2.4.25, but alsaconf don't detect the audio device.
With enabling the audio device located at 0:12.3 also the SMI stuff is enabled and shown under lspci. Eventually it have to enabled too, to get audio.
chris