coreboot

coreboot@coreboot.org

3 participants
39562 discussions

Re: Does anyone has text console or framebuffer working on SC1200 without VGA-BIOS ?
by Bernd Mödeker 24 Sep '03

24 Sep '03

Hi all, after googleling for "xpressloader" I found some information about the vga architecture of SC1200. All known VGA bioses need an VSA-Bios which emulates the standard vga registers and mappings. So Linuxbios is not able to use vga at SC1200. Also the framebuffer driver nsc.o (v 2.77) needs this VSA1 oder VSA2 bios. The only way to find out of this mess may be the use of XFree86 V4.x which directly uses the SC1200 hardware. But I had this not tested - yet. Here is the very interesting link: http://www.larwe.com/technical/geode_linux.html Bernd > -----Original Message----- > From: ron minnich [mailto:rminnich@lanl.gov] > Sent: Tuesday, September 23, 2003 11:12 PM > To: Bernd Mödeker > Subject: Re: Does anyone has text console or framebuffer working on > SC1200 without VGA-BIOS ? > > > make sure it is legal to send it before you send it. I don't want > something that is restricted in some way. > > Or else tell me where to get it. > > ron >

1 0

Re: Windows-based terminals - what can be done?
by elife elife 24 Sep '03

24 Sep '03

Hi stepan, Have you let linuxbios works with VGA support in your GX1 board ? Best Regards! >From: Stefan Reinauer <stepan(a)suse.de> >To: linuxbios(a)clustermatic.org >Subject: Re: Windows-based terminals - what can be done? >Date: Wed, 24 Sep 2003 10:28:19 +0200 > >* Peter Stuge <stuge-linuxbios(a)cdy.org> [030924 02:31]: > > On Tue, Sep 23, 2003 at 05:04:37PM -0400, Thomas Fritz wrote: > > > The board has an Award BIOS little square-like ROM, > > > > This is probably a regular flash ROM in a PLCC package. > > > > > and a larger 8MB ROM which holds Windows CE. > > > > What kind of ROM is this, exactly? Can you peel off the label and read > > what's printed on the chip(s)? > >probably a DiskOnChip, This looks like the GX1 board I have. > > >Best regards, > Stefan Reinauer > >-- >Architecture Team > SuSE Linux AG >_______________________________________________ >Linuxbios mailing list >Linuxbios(a)clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

2 1

Re: epia-m 600 -- still not working
by elife elife 24 Sep '03

24 Sep '03

Maybe you can dump data in init_bytes() to ensure they are the payload you want. >From: Niki Waibel <niki.waibel(a)newlogic.com> >Reply-To: Niki Waibel <niki.waibel(a)newlogic.com> >To: Andrew Ip <aip(a)cwlinux.com> >CC: ron minnich <rminnich(a)lanl.gov>, linuxbios(a)clustermatic.org >Subject: Re: epia-m 600 -- still not working >Date: Wed, 24 Sep 2003 11:09:06 +0200 (MEST) > >i just got a romimage from ian smith (thanks a lot!). >see this!!! >=== >LinuxBIOS-1.0.0 Tue Sep 23 21:19:35 BST 2003 starting... >Testing SDRAM : 00000000-0009ffff >SDRAM fill: >0009ffff >SDRAM verify: >0009ffff >Done. >Copying LinuxBIOS to ram. >000f0fd4 00004000 ffffffff >Jumping to LinuxBIOS. >000f0fd0 00006c8c ffeef6ff 010f2efa 00406115 0410ea00 18b80010 >00004000 010f2efa 00406115 4010ea00 00100000 000018b8 8ed88e00 >LinuxBIOS-1.0.0 Tue Sep 23 21:19:35 BST 2003 rebooting... >Finding PCI configuration type. >PCI: Using configuration type 1 >Scanning PCI bus...PCI: pci_scan_bus for bus 0 >PCI: 00:00.0 [1106/3123] >PCI: 00:01.0 [1106/b091] >PCI: 00:0d.0 [1106/3044] >PCI: 00:10.0 [1106/3038] >PCI: 00:10.1 [1106/3038] >PCI: 00:10.2 [1106/3038] >PCI: 00:10.3 [1106/3104] >PCI: 00:11.0 [1106/3177] >PCI: 00:11.1 [1106/0571] >PCI: 00:11.5 [1106/3059] >PCI: 00:12.0 [1106/3065] >PCI: 00:14.0 [8086/1229] >PCI: pci_scan_bus for bus 1 >PCI: pci_scan_bus returning with max=01 >PCI: pci_scan_bus returning with max=01 >done >Allocating PCI resources... >PCI: 00:00.0 register 10(00000008), read-only ignoring it >PCI: 00:00.0 register 10(00000008), read-only ignoring it >PCI: 00:00.0 register 10(00000008), read-only ignoring it >PCI: 00:00.0 register 10(00000008), read-only ignoring it >ASSIGN RESOURCES, bus 0 >PCI: 00:01.0 1c <- [0x00001000 - 0x00000fff] bus 1 io >PCI: 00:01.0 24 <- [0xfeb00000 - 0xfeafffff] bus 1 prefmem >PCI: 00:01.0 20 <- [0xfeb00000 - 0xfeafffff] bus 1 mem >PCI: 00:0d.0 10 <- [0xfeb01000 - 0xfeb017ff] mem >PCI: 00:0d.0 14 <- [0x00001800 - 0x0000187f] io >PCI: 00:10.0 20 <- [0x000018c0 - 0x000018df] io >PCI: 00:10.1 20 <- [0x000018e0 - 0x000018ff] io >PCI: 00:10.2 20 <- [0x00001c00 - 0x00001c1f] io >PCI: 00:10.3 10 <- [0xfeb02000 - 0xfeb020ff] mem >PCI: 00:11.1 20 <- [0x00001c20 - 0x00001c2f] io >PCI: 00:11.5 10 <- [0x00001000 - 0x000010ff] io >PCI: 00:12.0 10 <- [0x00001400 - 0x000014ff] io >PCI: 00:12.0 14 <- [0xfeb03000 - 0xfeb030ff] mem >PCI: 00:14.0 10 <- [0xfeb00000 - 0xfeb00fff] mem >PCI: 00:14.0 14 <- [0x00001880 - 0x000018bf] io >PCI: 00:14.0 18 <- [0xfea00000 - 0xfeafffff] mem >ASSIGNED RESOURCES, bus 0 >done. >Enabling PCI resourcess...PCI: 00:00.0 cmd <- 06 >PCI: 00:01.0 cmd <- 07 >PCI: 00:0d.0 cmd <- 83 >PCI: 00:10.0 cmd <- 01 >PCI: 00:10.1 cmd <- 01 >PCI: 00:10.2 cmd <- 01 >PCI: 00:10.3 cmd <- 02 >PCI: 00:11.0 cmd <- 87 >PCI: 00:11.1 cmd <- 07 >PCI: 00:11.5 cmd <- 01 >PCI: 00:12.0 cmd <- 83 >PCI: 00:14.0 cmd <- 03 >done. >Initializing PCI devices... >PCI devices initialized >totalram: 127M >Initializing CPU #0 >Enabling cache... >Setting fixed MTRRs(0-88) type: UC >Setting fixed MTRRs(0-16) type: WB >DONE fixed MTRRs >Setting variable MTRR 0, base: 0MB, range: 64MB, type WB >Setting variable MTRR 1, base: 64MB, range: 32MB, type WB >Setting variable MTRR 2, base: 96MB, range: 16MB, type WB >Setting variable MTRR 3, base: 112MB, range: 8MB, type WB >Setting variable MTRR 4, base: 120MB, range: 4MB, type WB >Setting variable MTRR 5, base: 124MB, range: 2MB, type WB >DONE variable MTRRs >Clear out the extra MTRR's >call intel_enable_fixed_mtrr() >call intel_enable_var_mtrr() >Leave setup_mtrrs >done. > >Max cpuid index : 1 >Vendor ID : CentaurHauls >Processor Type : 0x00 >Processor Family : 0x06 >Processor Model : 0x07 >Processor Mask : 0x00 >Processor Stepping : 0x03 >Feature flags : 0x00803035 > > >MTRR check >Fixed MTRRs : Enabled >Variable MTRRs: Enabled > >Disabling local apic...done. >CPU #0 Initialized >Mainboard fixup >Final mainboard fixup >Southbridge fixup >setting firewire >Assigning IRQ 10 to 0:d.0 > Readback = 10 >setting usb >Assigning IRQ 11 to 0:10.0 > Readback = 11 >Assigning IRQ 10 to 0:10.1 > Readback = 10 >Assigning IRQ 12 to 0:10.2 > Readback = 12 >Assigning IRQ 5 to 0:10.3 > Readback = 5 >setting ethernet >Assigning IRQ 11 to 0:12.0 > Readback = 11 >setting pci slot >Assigning IRQ 10 to 0:14.0 > Readback = 10 >setting vt8235 slot >Assigning IRQ 5 to 0:11.1 > Readback = 5 >Assigning IRQ 12 to 0:11.5 > Readback = 12 >Checking IRQ routing tables... >/home/ian/work/optos/linuxbios/cvs/freebios/src/arch/i386/lib/pirq_routing.c: 0 >done. >Copying IRQ routing tables to 0xf0000...done. >Verifing priq routing tables copy at 0xf0000...failed >Wrote linuxbios table at: 00000500 - 00000674 checksum 40ff > >Welcome to elfboot, the open sourced starter. >January 2002, Eric Biederman. >Version 1.2 > > 37:init_bytes() - zkernel_start:0xfffc0000 zkernel_mask:0x0000ffff >Cannot Load ELF Image >=== > >so it seems that mem config, copy to mem, mem itself and jump to mem are okay. >maybe my compiler or the binutils have done some fuckup. > >niki > >On 24-Sep-2003 Andrew Ip wrote: > > Hi, > > > >> no. executed memtest86 from lilo -- not as payload. > >> as i sayed, the payload code is not executed / not reached. > >> linuxbios seems to stop in c_start.s and it never reaches > >> src/arch/i386/lib/hardwaremain.c (i think so, because there > >> are some printk's in harwaremain which i never see on the > >> serial console). > > You probably want to copy the 0:00.0 pci register setting > > to the raminit.inc. Most likly is the memory bank/type causing > > the problem. > > > > -Andrew > > > > -- > > Andrew Ip > > Email: aip(a)cwlinux.com > > Tel: (852) 2542 2046 > > Fax: (852) 2542 2036 > > Mobile: (852) 9201 9866 > > > > Cwlinux Limited > > Unit 202B 2/F Lai Cheong Factory Building, > > 479-479A Castle Peak Road, > > Lai Chi Kok, Kowloon, > > Hong Kong. > > > > For public pgp key, please obtain it from http://www.keyserver.net/en. > >-- >niki w. waibel - system administrator @ newlogic technologies ag >_______________________________________________ >Linuxbios mailing list >Linuxbios(a)clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn

1 0

Possible bug in DDR SDRAM init code for VT8623?
by Ian Smith 24 Sep '03

24 Sep '03

I've been working on bringing up Linuxbios on a board which is based closely on the EPIA-M and I think I may have found a bug in the DDR SDRAM init code in src/northbridge/via/vt8623/raminit.inc The VIA Northbridge data sheet says that as part of the DDR init sequence you need to read from specific addresses on the bank but I think the registers to do these reads are not being set up properly which can cause the RAM test to fail. I adjusted a number of register settings to be the same as a sample Award Bios but it made no difference so I took a closer look at the DDR and found that %ecx was being set up with the memory location to read from instead of %esi. The diff for my fix is as follows: Index: src/northbridge/via/vt8623/raminit.inc =================================================================== RCS file: /cvsroot/freebios/freebios/src/northbridge/via/vt8623/raminit.inc,v retrieving revision 1.5 diff -r1.5 raminit.inc 85c85 < movl $0x2000, %ecx --- > movl $0x2000, %esi /* IAS changed from ecx to esi */ 89c89 < movl $0x800, %ecx --- > movl $0x800, %esi /* IAS changed from ecx to esi */ 119c119 < movl $0x350, %ecx --- > movl $0x350, %esi /* IAS changed from ecx to esi */ What is odd is that the original code works fine on the Via reference board (same design as EPIA-M) but when I try to run it on my customer board it fails until I make these changes. Does anyone with more knowledge than me of the Via chipsets have any ideas about this? Cheers Ian

3 2

Windows-based terminals - what can be done?
by Thomas Fritz 24 Sep '03

24 Sep '03

I have access to a few WBTs at a surplus place, and I've dug up the specs on them: Cyrix Pentium clone - 266MHz up to 128MB SDRAM ports: PS/2 keyb/mouse, 2 USB 1.1, 2 serial, 1 parallel, 10/100 ethernet, and sound in/out the chipset(s) include a SuperIO 97317, and a CS5530 (which handles the soundblaster compatible sound and presumably the video). The board has an Award BIOS little square-like ROM, and a larger 8MB ROM which holds Windows CE. There are also various places on the board which could have had various optional features, but there is no IDE, floppy, etc...but I think if I solder on a PCI slot where it belongs I could hack some more funtionality onto it for testing. I've been thinking of how to go about hacking this thing, and the easiest method I'd like to try first: Burning a new ROM to replace the Windows CE version. I doubt this thing would be easy to flash the BIOS, if it even had that capability. I'm not looking for graphics, a text screen will be more than sufficient. On this, I have two questions: What's my chances for success (educated guesses?), and has anyone done something similar?

3 2

EPIA-M serial port information
by Dave Ashley 24 Sep '03

24 Sep '03

Based on some emails from Andrew I started poking around into the epia-m serial port problem. Here are my observations: The 9 pin internal serial port is part of the VT1211 chip, not the VT8235, or other chips with serial ports. Under linux all baud rates are 1/2 what they should be. So if I pick 115200, I get 57600. If I pick 19200, I get 9600, etc. I can fix linux with setserial /dev/ttyS0 baud_base 57600 Then the actual baud rate matches what I expect. 38400 and 115200 cannot be achieved though. Andrew says if he boots with Award and the warm boots into linuxbios, the serial port is 115200. On the epia-m motherboard near the VT1211 chip is a crystal oscillator labeled KTS24.5X1K, which suggests it is 24.5 mhz. The VT1211 spec calls for a 48 mhz clock. Don't know if this is the cause of the problem, VT1211 being driven by 1/2 speed clock. My guess is there is some register in the VT1211 that has to be tweaked to specify the serial port clock divisor. linuxbios doesn't touch this at all. award bios sets it to match the 24.5 mhz crystal. On cold startup the vt1211 defaults to assuming 48 mhz input clock. This explains all observations, but doesn't solve the problem... I just put a scope on pin 17 of the vt1211, it appears to be 48 mhz though so that blows that theory.

2 1

about util/vgabios
by elife elife 23 Sep '03

23 Sep '03

Hi, I am trying util/vgabios but encounter a strange problem: testbios seems fetching wrong instruction [root@linux vgabios]# ./testbios -s 64k -t ~/lb/500video.bios.bin running file /root/lb/500video.bios.bin No base specified. defaulting to 0xc0000 No initial code segment specified. defaulting to 0xc000 No initial instruction pointer specified. defaulting to 0x0003 Switching to single step mode. AX=00ff BX=0000 CX=0000 DX=0080 SP=fff8 BP=0000 SI=0000 DI=0000 DS=0040 ES=0000 SS=0030 CS=c000 IP=0005 NV UP DI PL NZ NA PO NC c000:0003 eb53 JMP 58 c000:3 - AX=00ff BX=0000 CX=0000 DX=0080 SP=fff8 BP=0000 SI=0000 DI=0000 DS=0040 ES=0000 SS=0030 CS=c000 IP=005a NV UP DI PL NZ NA PO NC c000:0058 0000 ADD [BX+SI],AL c000:58 - [root@linux lb]# od -x 500vi* |more 0000000 aa55 eb60 3753 3034 3030 c237 2a8a 522a 0000020 5345 5245 4556 2044 00b1 4f46 2052 4249 0000040 204d 4f43 504d 5441 4249 4c49 5449 2a59 0000060 2a2a a807 0000 1090 3130 302f 2f37 3032 0000100 3230 0000 2e31 3431 3c20 4144 203e 2020 0000120 3156 2033 2020 2020 83e9 075e 6f43 7970 testbios said c000:0058 is 0000 but in file, it's E9835E JMP 5EDE Best Regards! _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

8 32

the EPIA universe
by ron minnich 23 Sep '03

23 Sep '03

I find myself getting confused about all the EPIA boards and their configurations. Can someone help fill this in? name CPU Extension Speed RAM EPIA-M C3 3DNOW 800 Mhz SDRAM That's all I know :-) ron

11 17

unsupported int on Epia800
by Nathanael Noblet 23 Sep '03

23 Sep '03

Hello, I'm still not sure what is causing it yet. I know it happens when I seem to turn on my epia board after it being off for awhile, while looking only at the screen and not the serial console. I get these message biosint: Unsupported int #0xff ... register settings... ... register settings... biosint: Unsupported int #0xfc ... register settings... ... register settings... biosint: Unsupported int #0xcd ... register settings... ... register settings... once I go back to look at the serial output because nothing is coming on screen. If I am viewing the output on serial, and turn it off then back on. This works. I always have linux shutdown cleanly and then power off. So I'm not sure what it is. I'm looking through that link posted earlier about BIOS Ints but haven't found these ones yet. Earlier when I was first getting this to work with my board I had had messages like these, only different ones I wrote them down biosint: Unsupported int #0xf7 ... register settings... ... register settings... biosint: Unsupported int #0xfc ... register settings... ... register settings... biosint: Unsupported int #0xc4 ... register settings... ... register settings... Ideas? -- Nathanael Noblet Gnat Solutions 4604 Monterey Ave NW Calgary, AB T3B 5K4 T/F 403.288.5360 C 403.809.5368 http://www.gnat.ca/

2 1

Re: the EPIA universe
by Michael Fenner 23 Sep '03

23 Sep '03

> Date: Tue, 23 Sep 2003 23:54:10 +0800 > From: Andrew Ip <aip(a)cwlinux.com> > To: ron minnich <rminnich(a)lanl.gov> > Cc: Niki Waibel <niki.waibel(a)newlogic.com>, linuxbios(a)clustermatic.org > Subject: Re: the EPIA universe > > Hi, > > > name CPU Extension Speed RAM remarks > > EPIA-M C3 3DNOW 800 Mhz SDRAM > > EPIA-M C3 3DNOW 600 MHz SDRAM fanless > I think all EPIA-M uses ddr, and EPIA/EPIA-V uses sdram. Also, > any CPU less or equal to 600MHz doesn't come with fan. Furthermore, > EPIA-M comes with MPEG-2 decoder. VIA has released source code for > mpeg-2 is and also X driver recently. If you want to try mpeg-2 decoder, > the easiest way is to use mplayer which just has got it supported. > AFAIK, EPIA-M 10000 is able to play mpeg-2 even without using the hw > decoder. > > -Andrew > Hi Andrew, where did you get the information that mplayer now supports the mpeg-2 decoder for the epia-m? Couldn't find it anywhere..... Also I'm a little confused about the source for the mpeg-2 decoder - I just know that they support a precompiled version of xine (called VeXP) for some Linux distributions and the source of the lite version of the CLE266 drivers (without hw-mpeg2). Did I miss some good news here? thnax, Michael

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot