coreboot October 2006

coreboot@coreboot.org

53 participants
208 discussions

Re: [LinuxBIOS] Improvements to "Supported Motherboards" wiki page.
by Uwe Hermann 01 Nov '06

01 Nov '06

On Tue, Oct 31, 2006 at 09:54:50AM -0700, ron minnich wrote: > >> Technologic TS5300 > > sorta working. Works last time I checked. OK, I'll make this read "OK" and be yellow. > >Totalimpact Briq > > dead company That doesn't necessarily mean anything. Does it actually work? Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org

2 1

Re: [LinuxBIOS] Tyan s2892 the OLPC way
by Lu, Yinghai 31 Oct '06

31 Oct '06

Add patch to mkelfImage to take vmlinux. Actually the vmlinux on amd64 is elf64, so parse it and set it back to elf32. With usb, and sata, and ide disk/CD...left 180k for kexec tools YH

1 0

[LinuxBIOS] Support for Intel G965 GMCH Chipset?
by Chris Ziomkowski 31 Oct '06

31 Oct '06

I am investigating options for an embedded systems project which we need to launch Q1 next year. I found linuxbios and love the idea. I have a few concerns though, and I thought someone here might be able to help me decide how difficult it might be to go this route. First, all of the mainboards that I can find which fit our requirements use the Intel G965 GMCH chipset. (Requirements are mini ITX format, Intel Core 2 Duo desktop processor support, not socket 478, and dual Gbit LAN. I've only found 3 products after a week of searching. ) Chipset docs are available at http://www.intel.com/support/graphics/intelg965/ The G965 is not listed as supported, and I've been unable to find any comforting comments in the list archives. I am an accomplished embedded systems programmer, but my time is stretched very thin on this project. Do you guys believe I will be able to make this work without heroic efforts? Second, the mainboards all come with an 8 Mbit BIOS flash. Will this be enough to boot Linux directly? There is no IDE capability on these boards, so the only disk options are USB or SATA. I don't need video support. There will only be a serial console. Assuming I can boot direct to Linux from the BIOS, would SATA or USB be more appropriate for loading the rest of the system? Any comments would be appreciated. Am I getting in over my head? Do you think linuxbios is stable enough to consider for a commercial product? Thanks, Chris

6 8

[LinuxBIOS] [PATCH] Rename ITE -> ite in the code.
by Uwe Hermann 31 Oct '06

31 Oct '06

Rename some variables from *ITE* to *ite* for consistency reasons (refs #4). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> --- Tested with abuild. No need to rename a directory this time, it's already called ite/ (not ITE/). Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org

2 2

Re: [LinuxBIOS] [Etherboot-discuss] USB Bootloader
by Lu, Yinghai 31 Oct '06

31 Oct '06

MB:? FLASH size? YH

1 0

[LinuxBIOS] USB Bootloader
by jean raymond 31 Oct '06

31 Oct '06

Hello, I tried filo 0.4 from openbios.org, which was able to ide boot but hangs on usb boot with this: Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3 rom_stream: 0xfffe0000 - 0xfffeffff Found ELF candiate at offset 0 header_offset is 0 Header addresap[1].size = 0x9f390, mem->map[1].type = 0x1 n_type: 00000001 n_name(8): ELFBoot n_desc(10): Etherboot n_type: 00000002 n_name(8): ELFBoot n_desc(6): 5.4.2 Loading Etherboot version: 5.4.2 access the elf segments Dropping non PT_LOAD segment malloc Enter, size 32, free_mem_ptr 00122d0c malloc 0x00122d0c New segment addr 0x10000 size 0x430c0 offset 0x0 filesize 0xcc90 (cleaned up) New segment addr 0x10000 size 0x430c0 offset 0x0 filesize 0xcc90 lb_start : 0x0000000000100000, lb_end : 0x000000000012a000) start : 0x0000000000010000, middle : 0x000000000001cc90, end : 0x00000000000530c0 Load the segments Loading Segment: addr: 0x0000000000010000 memsz: 0x00000000000430c0 filesz: 0x000000000000cc90 dest:0x0000000000010000, middle:000000000001cc90, end:0x00000000000530c0, start_offset:0000000000000000, offset:0000000000000000 Skip the unused bytes Copy data from the initial buffer dest:0x0SOLE_BTEXT pci_init Scanning PCI: found 28 devices function allot, address = bffffc70 allot(0) function allot, address = bffffc60 Boot from (N)etwork (D)isk or (Q)uit? D Answer : Disk device present boot = 0x00000001, type = 1, failsafe = 0 function allot, address = bffffc60 Probing pci disk... [FILO]boot eax = 0xe1040170 boot ebx = 0x00800401 boot arg = 0x00000000 FILO version 0.4.1 (root@frlanzf00595) Tue Oct 31 17:00:24 CET 2006 Press <Enter> for default boot, or <Esc> for boot prompt... boot: uda1:/bzImage root=/dev/sda2 console=tty0 console=ttyS0,115200 dev=uda1, path=/bzImage name = uda1, type = 3, drive = 0, part = 1, offset = 0x00000000, length = 0x00000000 LinuxLabs USB bootloader Resetting UHCI uhc_init setting framelist to: 000101b0 Starting UHCI HCI at 000030c0 Resetting UHCI uhc_init setting framelist to: 000101b0 Starting UHCI HCI at 000030e0 frame_list is at bffede50 frame_list_link: addr: fffefe50 frame_list_link: raw addr: 00000800 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000000 frame_list_link: depth: 00000000 frame_list is at bffebe50 frame_list_link: addr: ffff0650 frame_list_link: raw addr: 00000040 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000000 frame_list_link: depth: 00000000 New USB device, setting address 2 port = 0x000030d0 controller =0x00000000 lowspeed = 0 next_usb_dev = 0x00000003 addr = 0x00000002 uhci_control_msg: request_type = 00000000 request = 00000005 wLength=0 ctrl_msg( 00000000, 00000000, 00000005, 00000002, 00000000, 00000000, p) 0 bytes in payload lowspeed = u HCI at 000030c0 failed_transaction: TD(0002e5a0): failed_transaction: type: SETUP failed_transaction: retries: 00000003 failed_transaction: IOC failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000000 failed_transaction: max_transfer: 00000007 failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: 0002e5c0 failed_transaction: raw addr: 0003e770 failed_transaction: terminate: 00000000 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 failed_transaction: TD(0002e5c0): failed_transaction: type: IN failed_transaction: retries: 00000000 failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000001 failed_transaction: max_transfer: 000007ff failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: fffefe50 failed_transaction: raw addr: 00000000 failed_transaction: terminate: 00000001 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 configure_device: set_address failed! value = 0x00001080 poll_usb 1 hc_type[1] = 00000000 ... There is a USB device, but it won't init! This is a bad thing. failed to open usb boot: uda1:/bzImage root=/dev/sda2 console=tty0 console=ttyS0,115200 Now, how can etherboot-filo be fixed to boot at all? And, how can filo 0.5 be fixed to boot USB? Thanks! _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

1 0

[LinuxBIOS] [PATCH] Do not hardcode iasl path.
by Uwe Hermann 31 Oct '06

31 Oct '06

Change the path to iasl from '/usr/sbin/iasl' to 'iasl' in order to not hardcode it in the config files. The path is different on Debian, for example (closes #9). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> --- Can somebody please test (on SUSE?) whether this works as expected, or whether /usr/sbin needs to be added to PATH somewhere... Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org

3 5

Re: [LinuxBIOS] Tyan s2892 the OLPC way
by Lu, Yinghai 31 Oct '06

31 Oct '06

Ron, Where is patch for mkelfImage that can take vmlinux instead of bzImage? YH ________________________________ From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of ron minnich Sent: Sunday, October 29, 2006 6:34 PM To: yhlu Cc: myles(a)mouselemur.cs.byu.edu; LinuxBIOS Subject: Re: [LinuxBIOS] Tyan s2892 the OLPC way On 10/29/06, yhlu <yinghailu(a)gmail.com> wrote: but the one still include VSA and linuxbios in it. busybox you want this. kernel kexec-boot-loader you want this kexec-tools mkelfimage uclibc do i need kexec-boot-loader? yes If you look in deploy, for now, you can use the payload, which is built without containing linuxbios or vsa. That is how I got a working payload for ultra40. What we need to do with buildrom is extend it so we can have a config file for a given platform, that builds the proper kernel AND linuxbios, and has payloads like VSA as an OPTION. I think this is easy. I did it (sort of) for qemu. ron

4 4

Re: [LinuxBIOS] Tyan s2892 the OLPC way
by Lu, Yinghai 30 Oct '06

30 Oct '06

Please check the attachment, it can make uclibc build automatically. YH

1 0

Re: [LinuxBIOS] Tyan s2892 the OLPC way
by Lu, Yinghai 30 Oct '06

30 Oct '06

Good, I will try it with my 2M Rom emulator. Thanks Yinghai Lu -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Myles Watson Sent: Monday, October 30, 2006 10:05 AM To: 'yhlu' Cc: linuxbios(a)linuxbios.org Subject: Re: [LinuxBIOS] Tyan s2892 the OLPC way Here is the tarball, resolve.S (needed for uclibc), and a patch from the OLPC buildrom. I haven't made it totally automated. I just have a symbolic link to the payload generated in the deploy directory from my other LinuxBIOS directory. resolve.S needs to be copied into buildrom/work/uclibc/uClibc-0.9.28/ldso/ldso/x86_64/resolve.S Otherwise uclibc will not build. Myles > -----Original Message----- > From: yhlu [mailto:yinghailu@gmail.com] > Sent: Monday, October 30, 2006 9:48 AM > To: myles(a)mouselemur.cs.byu.edu > Subject: Re: [LinuxBIOS] Tyan s2892 the OLPC way > > please. > > On 10/30/06, Myles Watson <myles(a)pel.cs.byu.edu> wrote: > > I can send it to you if you want, but there are very few modifications > from > > the original. > > > > I built it all in a 64-bit environment once I had it working. > > > > I got rid of kexec-boot-loader and included a statically linked kexec. > It > > saved some space in the ROM for me. > > > > I guess I don't know enough about .elf.lzma and what's going on > underneath. > > I just let buildrom take care of it for me. > > > > Myles > > > > > -----Original Message----- > > > From: yhlu [mailto:yinghailu@gmail.com] > > > Sent: Sunday, October 29, 2006 11:08 PM > > > To: ron minnich; myles(a)mouselemur.cs.byu.edu > > > Cc: Lu, Yinghai > > > Subject: Re: [LinuxBIOS] Tyan s2892 the OLPC way > > > > > > Can you send me your buildrom tar ball to me? > > > > > > Also for .elf.lzma, do you need one new mkelfImage to build elf with > > > uncompress kernel and initrd? > > > > > > Also I hope I can build it under 64bit environment. > > > > > > Thanks > > > > > > Yinghai Lu > > > > > >

1 0

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