coreboot September 2006

coreboot@coreboot.org

52 participants
173 discussions

[LinuxBIOS] r2419 - trunk/LinuxBIOSv2/src/northbridge/amd/gx2
by svn＠openbios.org 18 Sep '06

18 Sep '06

Author: rminnich Date: 2006-09-18 06:23:23 +0200 (Mon, 18 Sep 2006) New Revision: 2419 Modified: trunk/LinuxBIOSv2/src/northbridge/amd/gx2/raminit.c Log: A fix for hynix dram problems seen at 366/244 Modified: trunk/LinuxBIOSv2/src/northbridge/amd/gx2/raminit.c =================================================================== --- trunk/LinuxBIOSv2/src/northbridge/amd/gx2/raminit.c 2006-09-15 23:14:37 UTC (rev 2418) +++ trunk/LinuxBIOSv2/src/northbridge/amd/gx2/raminit.c 2006-09-18 04:23:23 UTC (rev 2419) @@ -85,6 +85,14 @@ /* load RDSYNC */ msr = rdmsr(0x2000001f); msr.hi = 0x000ff310; + /* the above setting is supposed to be good for "slow" ram. We have found that for + * some dram, at some clock rates, e.g. hynix at 366/244, this will actually + * cause errors. The fix is to just set it to 0x310. Tested on 3 boards + * with 3 different type of dram -- Hynix, PSC, infineon. + * I am leaving this comment here so that at some future time nobody is tempted + * to mess with this setting -- RGM, 9/2006 + */ + msr.hi = 0x00000310; msr.lo = 0x00000000; wrmsr(0x2000001f, msr);

1 0

[LinuxBIOS] First Time User ; LinuxBIOS Build Broken
by rum vodka 17 Sep '06

17 Sep '06

Am first time user of LinuxBIOS though I have been introduced long time ago. After going thru' QEMU build tutorial from LinuxBIOS website, downloaded and started building the packages in the order given. mkelfImagev2.7 build went thru without problems (Am using vmlinuz and initrd of Linux kernel 2.6.15 or 2.6.17) LinuxBIOSV2-2405 was the next. As per the doc, edited ROM_SIZE and the laoction of linux.elf. After running buildtarget without problems, make failed with the following errors. <snip> gcc -m32 -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o nm -n linuxbios | sort > linuxbios.map objcopy --gap-fill 0xff -O binary linuxbios linuxbios.strip cp -f /lnx_data/lnx_apps/QEMU/mkelfImage-2.7/linux.elf payload ./buildrom linuxbios.strip linuxbios.rom payload 0x10000 0x200000 payload (2527194) + linuxbios (65536) size larger than ROM (2097152) size! make[1]: *** [linuxbios.rom] Error 1 make[1]: Leaving directory `/lnx_data/lnx_apps/QEMU/LinuxBIOSv2-2405/targets/emulation/qemu-i386/qemu-i386/image' make: *** [image/linuxbios.rom] Error 1 <snip> Would like to have at least the Kernel v2.6.15 into LinuxBIOS. Any ideas how it is possible to accomodate this ? /Ramanathan

4 5

[LinuxBIOS] pci_level_irq: lower order bits are wrong: want 0x0, got 0x20
by Peter Stuge 17 Sep '06

17 Sep '06

Since the first boot with LB I've always seen this in the output: --8<-- pci_routing_fixup: dev is 000104c0 setting firewire setting usb Assigning IRQ 5 to 0:10.0 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 9 to 0:10.1 Readback = 9 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 9 to 0:10.2 Readback = 9 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 5 to 0:10.3 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting vt8235 Assigning IRQ 5 to 0:11.1 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 9 to 0:11.5 Readback = 9 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting ethernet Assigning IRQ 5 to 0:12.0 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting vga Assigning IRQ 5 to 1:0.0 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting pci slot setting cardbus slot Assigning IRQ 5 to 0:a.0 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 9 to 0:a.1 Readback = 9 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting riser slot PNP: 002e.0 init PNP: 002e.1 init PNP: 002e.2 init PNP: 002e.3 init PNP: 002e.b init PCI: 00:11.1 init Enabling VIA IDE. ide_init: enabling compatibility IDE addresses enables in reg 0x42 0x0 enables in reg 0x42 read back as 0x0 -->8-- I'm having a few problems with the CF card, but they are probably related to pcmcia things in the kernel. I'm about to talk to linux-pcmcia but wanted some input on those 0x20 messages first.. ..because if I force Linux to look for the CF card (0:a.1) with ide2=0x1e0,0x1ec,9 I get: --8<-- hde: probing with STATUS(0x50) instead of ALTSTATUS(0x00) hde: SAnDiSk, CFA DISK drive ide4: I/O resource 0x1E0-0x1E7 not free. ide4: ports already in use, skipping probe ide2 at 0x1e0-0x1e7,0x1ec on irq 9 hde: max request size: 128KiB hde: 985056 sectors (504 MB) w/1KiB Cache, CHS=1986/16/31 hde:<4>hde: lost interrupt hde: lost interrupt hde: lost interrupt -->8-- Note SAnDiSk vs. SanDisk - bit 5 (0x20) is jammed high on a few bytes.. (plus this is a brand new Extreme III 1GB CF, not 504MB) --8<-- FILO version 0.5 (stuge@carepad4) Sat Sep 16 18:00:42 CEST 2006 boot: hde1:/bzImage root=/dev/hde1 ro console=tty0 console=ttyS0,115200 hde: LBA 1025MB: SAnDiSk Unknown filesystem type boot: hde1:/bzImage root=/dev/hde1 ro console=tty0 console=ttyS0,115200 -->8-- At one point I did get "SanDisk" out of FILO (the CF that I thought I busted turned out to work after all) but I didn't think much of it until now and so don't recall the exact circumstances. I recall needing to unplug the power cable and let the board sit for a while and then only on the first boot would I get "SanDisk" properly. I need to experiment more with this. (This was also before Nick's recent changes to the rl5c476 IRQ fixes.) Speaking about the 5c476, I've also gotten: cs: pcmcia_socket0: unable to apply power (as seen on http://www.kernel.org/pub/linux/utils/kernel/pcmcia/powerbugs.html) when inserting cards. This is on 2.6.18rc7, I've been experimenting with 2.6.17.6 and 2.6.18rc6 as well. Some combination has worked. I'm set for a day of testing to make a matrix of what works and what doesn't. But if anyone can provide insight into the mysterious 0x20 bit I'd appreciate it. Best case it will even narrow my search. //Peter

2 3

[LinuxBIOS] FILO problems with an NCD ThinStar terminal
by Adam Nielsen 17 Sep '06

17 Sep '06

Hi everyone, I'm playing around with an old NCD ThinStar 300 terminal, and I'd like to see if I can some custom code going on it so that I can do something useful with it. The terminal has an Intel CPU (sorry, can't recall which one it is at the moment) but appears to be an i440BX chipset. When switching the unit on I can get into the boot monitor and then do a network boot, and I've now figured out the exact header needed to get the unit to accept boot images (they're in ELF format, but they need certain bytes set at the start, and the image has to load at a certain address.) I managed to boot an image I compiled in C (with an assembly loader tacked on the front) and I was able to send a few bytes out over the serial port. I was about to embark on trying to install LinuxBIOS when I stumbled across FILO. I thought I'd try to run FILO directly from my loader first as the LinuxBIOS configuration looked rather scary, and while I was playing around with it (and much to my surprise) the terminal will boot the FILO ELF loader directly! Unfortunately there are a few issues with FILO, and it turned out that when I enabled debugging mode I had to add my loader onto the start anyway otherwise the terminal complained about CRC errors (one of the flags in my loader tells the unit to skip the CRC check.) Anyway, this worked, and I got to the point where FILO looks for a menu file, but then it got stuck. I tried using a menu.lst file so that I could specify a serial terminal, but I had to embed the menu.lst file into the ELF image (as I was hoping that the ELF loader would then load menu.lst into RAM) and this appears to have worked, as FILO is now telling me to "Press any key to continue" over the serial line. Unfortunately as soon as I do press a key it locks up. It even locks up if I press the Shift key on the unit's keyboard, making me wonder if there's some problem with the IRQs pointing to the wrong address. It may even be that I've just embedded the menu.lst file incorrectly - how does everyone else embed theirs? It worries me that half the contents of the menu.lst file along with some garbage is dumped over the serial port before the debug messages start appearing. In fact, I just realised that it's ignoring the baud rate I'd set in that file, so I don't think it's being read at all. Anyway, if anyone has any advice, I'm all ears! See below for the debug output. Thanks, Adam. collect_sys_info: boot eax = 0x100000 collect_sys_info: boot ebx = 0x800 collect_sys_info: boot arg = 0x4254 collect_linuxbios_info: Searching for LinuxBIOS tables... Can't get memory map from firmware. Using hardcoded default. malloc_diag: alloc: 0 bytes (0 blocks), free: 16376 bytes (1 blocks) malloc_diag: alloc: 40 bytes (1 blocks), free: 16336 bytes (1 blocks) collect_sys_info: 0000000000000000-00000000000a0000 collect_sys_info: 0000000000100000-0000000001000000 collect_sys_info: RAM 16 MB relocate: Current location: 0x100040-0x1442c7 relocate: Relocating to 0xfbbd70-0xfffff7... ok setup_timers: CPU 134 MHz pci_init: Scanning PCI: found 7 devices malloc_diag: alloc: 136 bytes (2 blocks), free: 16240 bytes (1 blocks) pci_init: 00:00.0 8086:7100 0600 00 pci_init: 00:06.0 8086:1229 0200 00 pci_init: 00:07.0 8086:7110 0601 00 pci_init: 00:07.1 8086:7111 0101 80 pci_init: 00:07.2 8086:7112 0c03 00 pci_init: 00:07.3 8086:7113 0680 00 pci_init: 00:08.0 5333:8904 0300 00 menu: mem@0x300000 malloc_diag: alloc: 160 bytes (3 blocks), free: 16216 bytes (1 blocks) file_open: dev=mem@0x300000, path=<NULL> parse_device_name: offset=0x300000 length=0x0 devopen: after offset: start 6144, length 8382464 malloc_diag: alloc: 136 bytes (2 blocks), free: 16240 bytes (1 blocks) Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. Press any key to continue. ... (I had to change the RAM from 32MB down to 16MB as this is all the unit has, and it locked up otherwise, as you might expect.)

2 6

[LinuxBIOS] r2418 build service
by LinuxBIOS information 16 Sep '06

16 Sep '06

Dear LinuxBIOS readers! This is the automated build check service of LinuxBIOS. The developer "stepan" checked in revision 2418 to the LinuxBIOS source repository and caused the following changes: Change Log: run preprocessor on hand-crafted config files in abuild, too Build Log: Compilation of artecgroup:dbe61 is still broken If something broke during this checkin please be a pain in stepan's neck until the issue is fixed. If this issue is not fixed within 24h the revision will be backed out. Yours truely, LinuxBIOS automatic build system

1 0

[LinuxBIOS] r2418 - in trunk/LinuxBIOSv2: targets/via/epia-m util/abuild
by svn＠openbios.org 16 Sep '06

16 Sep '06

Author: stepan Date: 2006-09-16 01:14:37 +0200 (Sat, 16 Sep 2006) New Revision: 2418 Modified: trunk/LinuxBIOSv2/targets/via/epia-m/Config-abuild.lb trunk/LinuxBIOSv2/util/abuild/abuild.sh Log: run preprocessor on hand-crafted config files in abuild, too Modified: trunk/LinuxBIOSv2/targets/via/epia-m/Config-abuild.lb =================================================================== --- trunk/LinuxBIOSv2/targets/via/epia-m/Config-abuild.lb 2006-09-15 17:00:11 UTC (rev 2417) +++ trunk/LinuxBIOSv2/targets/via/epia-m/Config-abuild.lb 2006-09-15 23:14:37 UTC (rev 2418) @@ -7,9 +7,8 @@ option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=1 -option ROM_SIZE=512*1024 +option ROM_SIZE=256*1024 - option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=1 @@ -28,16 +27,16 @@ # romimage "normal" option USE_FALLBACK_IMAGE=0 - option ROM_IMAGE_SIZE=0x20000 + option ROM_IMAGE_SIZE=64*1024 option LINUXBIOS_EXTRA_VERSION=".0-Normal" - payload /dev/null + payload PAYLOAD end romimage "fallback" option USE_FALLBACK_IMAGE=1 - option ROM_IMAGE_SIZE=0x20000 + option ROM_IMAGE_SIZE=64*1024 option LINUXBIOS_EXTRA_VERSION=".0-Fallback" - payload /dev/null + payload PAYLOAD end buildrom ./linuxbios.rom ROM_SIZE "normal" "fallback" Modified: trunk/LinuxBIOSv2/util/abuild/abuild.sh =================================================================== --- trunk/LinuxBIOSv2/util/abuild/abuild.sh 2006-09-15 17:00:11 UTC (rev 2417) +++ trunk/LinuxBIOSv2/util/abuild/abuild.sh 2006-09-15 23:14:37 UTC (rev 2418) @@ -85,22 +85,23 @@ TARGCONFIG=$LBROOT/targets/$VENDOR/$MAINBOARD/Config-abuild.lb # get a working payload for the board if we have one. + if [ -x $payloads/payload.sh ]; then PAYLOAD=`$payloads/payload.sh $VENDOR $MAINBOARD` + echo "Using custom payload $PAYLOAD" fi mkdir -p $TARGET if [ -f $TARGCONFIG ]; then cp $TARGCONFIG $TARGET/Config-${VENDOR}_${MAINBOARD}.lb - echo "Used existing test target $TARGCONFIG" + echo -n "Using existing test target $TARGCONFIG" xml " <config>$TARGCONFIG</config>" - return - fi + else - echo -n " Creating config file..." - xml " <config>autogenerated</config>" - ( cat << EOF + echo -n " Creating config file..." + xml " <config>autogenerated</config>" + ( cat << EOF # This will make a target directory of ./VENDOR_MAINBOARD target VENDOR_MAINBOARD @@ -111,8 +112,8 @@ option HOSTCC="CROSS_HOSTCC" EOF - if [ "$TARCH" == i386 ] ; then - cat <<EOF + if [ "$TARCH" == i386 ] ; then + cat <<EOF romimage "normal" option USE_FALLBACK_IMAGE=0 option ROM_IMAGE_SIZE=0x20000 @@ -128,22 +129,26 @@ end buildrom ./linuxbios.rom ROM_SIZE "normal" "fallback" EOF - else - cat <<EOF + else + cat <<EOF romimage "only" option LINUXBIOS_EXTRA_VERSION=".0" payload PAYLOAD end buildrom ./linuxbios.rom ROM_SIZE "only" EOF + fi + ) > $TARGET/Config-${VENDOR}_${MAINBOARD}.lb fi - ) | sed -e s,VENDOR,$VENDOR,g \ + + sed -i.pre -e s,VENDOR,$VENDOR,g \ -e s,MAINBOARD,$MAINBOARD,g \ -e s,PAYLOAD,$PAYLOAD,g \ -e s,CROSSCC,"$CC",g \ -e s,CROSS_PREFIX,"$CROSS_COMPILE",g \ -e s,CROSS_HOSTCC,"$HOSTCC",g \ - > $TARGET/Config-${VENDOR}_${MAINBOARD}.lb + $TARGET/Config-${VENDOR}_${MAINBOARD}.lb + echo " ok" }

1 0

[LinuxBIOS] r2417 build service
by LinuxBIOS information 15 Sep '06

15 Sep '06

Dear LinuxBIOS readers! This is the automated build check service of LinuxBIOS. The developer "stepan" checked in revision 2417 to the LinuxBIOS source repository and caused the following changes: Change Log: add option to build autobuild images with real payloads instead of /dev/null. Build Log: Compilation of artecgroup:dbe61 is still broken If something broke during this checkin please be a pain in stepan's neck until the issue is fixed. If this issue is not fixed within 24h the revision will be backed out. Yours truely, LinuxBIOS automatic build system

1 0

[LinuxBIOS] r2417 - trunk/LinuxBIOSv2/util/abuild
by svn＠openbios.org 15 Sep '06

15 Sep '06

Author: stepan Date: 2006-09-15 19:00:11 +0200 (Fri, 15 Sep 2006) New Revision: 2417 Modified: trunk/LinuxBIOSv2/util/abuild/abuild.sh Log: add option to build autobuild images with real payloads instead of /dev/null. Modified: trunk/LinuxBIOSv2/util/abuild/abuild.sh =================================================================== --- trunk/LinuxBIOSv2/util/abuild/abuild.sh 2006-09-15 14:53:55 UTC (rev 2416) +++ trunk/LinuxBIOSv2/util/abuild/abuild.sh 2006-09-15 17:00:11 UTC (rev 2417) @@ -84,6 +84,11 @@ TARCH=$( architecture $VENDOR $MAINBOARD ) TARGCONFIG=$LBROOT/targets/$VENDOR/$MAINBOARD/Config-abuild.lb + # get a working payload for the board if we have one. + if [ -x $payloads/payload.sh ]; then + PAYLOAD=`$payloads/payload.sh $VENDOR $MAINBOARD` + fi + mkdir -p $TARGET if [ -f $TARGCONFIG ]; then @@ -356,7 +361,7 @@ function myhelp { - echo "Usage: $0 [-v] [-a] [-b] [-t <vendor/board>] [lbroot]" + echo "Usage: $0 [-v] [-a] [-b] [-t <vendor/board>] [-p <dir>] [lbroot]" echo " $0 [-V|--version]" echo " $0 [-h|--help]" echo @@ -365,9 +370,11 @@ echo " [-a|--all] build previously succeeded ports as well" echo " [-b|--broken] attempt to build ports that are known broken" echo " [-t|--target <vendor/board>] attempt to build target vendor/board only" + echo " [-p|--payloads <dir>] use payloads in <dir> to build images" echo " [-V|--version] print version number and exit" echo " [-h|--help] print this help and exit" - echo " [-x|--xml] write xml log file $XMLFILE" + echo " [-x|--xml] write xml log file " + echo " (defaults to $XMLFILE)" echo " [lbroot] absolute path to LinuxBIOS sources" echo " (defaults to $LBROOT)" echo @@ -377,7 +384,7 @@ { cat << EOF -LinuxBIOS autobuild: V0.2. +LinuxBIOS autobuild: V0.3. Copyright (C) 2004 by Stefan Reinauer <stepan(a)openbios.org> Copyright (C) 2006 by coresystems GmbH <info(a)coresystems.de> @@ -396,7 +403,7 @@ verbose=false # parse parameters -args=`getopt -l version,verbose,help,all,target:,broken Vvhat:b -- "$@"` +args=`getopt -l version,verbose,help,all,target:,broken,payloads: Vvhat:bp: -- "$@"` if [ $? != 0 ]; then myhelp @@ -413,6 +420,7 @@ -v|--verbose) shift; verbose=true;; -V|--version) shift; myversion; exit 0;; -h|--help) shift; myhelp; exit 0;; + -p|--payloads) shift; payloads="$1"; shift;; --) shift; break;; -*) echo -e "Invalid option\n"; myhelp; exit 1;; *) break;;

1 0

[LinuxBIOS] r2416 build service
by LinuxBIOS information 15 Sep '06

15 Sep '06

Dear LinuxBIOS readers! This is the automated build check service of LinuxBIOS. The developer "rminnich" checked in revision 2416 to the LinuxBIOS source repository and caused the following changes: Change Log: fix variable name for ts5300 Signed-off-by: Ronald G. Minnich Build Log: Compilation of artecgroup:dbe61 is still broken Configuration of technologic:ts5300 has been fixed If something broke during this checkin please be a pain in rminnich's neck until the issue is fixed. If this issue is not fixed within 24h the revision will be backed out. Yours truely, LinuxBIOS automatic build system

1 0

[LinuxBIOS] r2416 - trunk/LinuxBIOSv2/src/mainboard/technologic/ts5300
by svn＠openbios.org 15 Sep '06

15 Sep '06

Author: rminnich Date: 2006-09-15 16:53:55 +0200 (Fri, 15 Sep 2006) New Revision: 2416 Modified: trunk/LinuxBIOSv2/src/mainboard/technologic/ts5300/Options.lb Log: fix variable name for ts5300 Signed-off-by: Ronald G. Minnich Modified: trunk/LinuxBIOSv2/src/mainboard/technologic/ts5300/Options.lb =================================================================== --- trunk/LinuxBIOSv2/src/mainboard/technologic/ts5300/Options.lb 2006-09-14 20:08:10 UTC (rev 2415) +++ trunk/LinuxBIOSv2/src/mainboard/technologic/ts5300/Options.lb 2006-09-15 14:53:55 UTC (rev 2416) @@ -134,7 +134,7 @@ default _RAMBASE = 0x00004000 -default CONFIG_COMPRESSED_ROM_STREAM = 1 +default CONFIG_COMPRESSED_ROM_STREAM_NRV2B = 1 default CONFIG_ROM_STREAM = 1 ##

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
18
Older →

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 September 2006