January 2006 - coreboot - mail.coreboot.org

Re: [LinuxBIOS] failure to execute via/epia with rev 2158
by Lu, Yinghai Jan. 17, 2006

Jan. 17, 2006

You may need to remove the Device pci 0.1 on end # AGP bridge YH

1 0

[LinuxBIOS] failure to execute via/epia with rev 2158
by Ronald G Minnich Jan. 17, 2006

Jan. 17, 2006

malloc Enter, size 668, free_mem_ptr 00018000 malloc 0x00018000 Capability: 0x07 @ 0x80 Capability: 0x08 @ 0x80 Capability: 0x10 @ 0x80 PCI: 00:01.0 [1106/8601] enabled PCI: devfn 0x10, bad id 0xffffffff PCI: devfn 0x18, bad id 0xffffffff PCI: devfn 0x20, bad id 0xffffffff PCI: devfn 0x28, bad id 0xffffffff PCI: devfn 0x30, bad id 0xffffffff PCI: devfn 0x38, bad id 0xffffffff PCI: devfn 0x40, bad id 0xffffffff PCI: devfn 0x48, bad id 0xffffffff PCI: devfn 0x50, bad id 0xffffffff PCI: devfn 0x58, bad id 0xffffffff PCI: devfn 0x60, bad id 0xffffffff PCI: devfn 0x68, bad id 0xffffffff PCI: devfn 0x70, bad id 0xffffffff PCI: devfn 0x78, bad id 0xffffffff PCI: devfn 0x80, bad id 0xffffffff PCI: 00:11.0 [1106/8231] bus ops PCI: 00:11.0 [1106/8231] enabled PCI: 00:11.1 [1106/0571] ops PCI: 00:11.1 [1106/0571] enabled PCI: 00:11.2 [1106/3038] disabled PCI: 00:11.3 [1106/3038] disabled PCI: 00:11.4 [1106/8235] ops PCI: 00:11.4 [1106/8235] disabled PCI: 00:11.5 [1106/3058] disabled PCI: 00:11.6 [1106/3068] enabled PCI: devfn 0x8f, bad id 0xffffffff PCI: 00:12.0 [1106/3065] ops PCI: 00:12.0 [1106/3065] enabled PCI: devfn 0x98, bad id 0xffffffff PCI: devfn 0xa0, bad id 0xffffffff PCI: devfn 0xa8, bad id 0xffffffff PCI: devfn 0xb0, bad id 0xffffffff PCI: devfn 0xb8, bad id 0xffffffff PCI: devfn 0xc0, bad id 0xffffffff PCI: devfn 0xc8, bad id 0xffffffff PCI: devfn 0xd0, bad id 0xffffffff PCI: devfn 0xd8, bad id 0xffffffff PCI: devfn 0xe0, bad id 0xffffffff PCI: devfn 0xe8, bad id 0xffffffff PCI: devfn 0xf0, bad id 0xffffffff PCI: devfn 0xf8, bad id 0xffffffff PCI: 00:00.1 PCI: Left over static devices. Check your Config.lb This is probably failing due to the check, which IIRC is new. But I'm not sure, anyone else seeing this? ron

1 0

Re: [LinuxBIOS] [Kboot-general] Re: small 64bit initrd
by Lu, Yinghai Jan. 17, 2006

Jan. 17, 2006

Kexec support 2.4? YH -----Original Message----- From: Richard Smith [mailto:smithbone@gmail.com] Sent: Wednesday, January 11, 2006 7:40 PM To: Werner Almesberger Cc: Ronald G Minnich; kboot-general(a)lists.sourceforge.net; linuxbios(a)openbios.org; Fastboot mailing list; Lu, Yinghai Subject: Re: [LinuxBIOS] [Kboot-general] Re: small 64bit initrd > > > > Getting 1 MB is as good as we can do for now. > > Hmm, that'll get awfully tight :-( Its tight but can be done. I've build a embedded system that booted out of 1Meg of flash. 2.4 kernel+initrd that loaded a pcmcia module for the wireless adapter in the system dhcp'ed up the network and then pulled down a larger ramfs and kexec'ed into it. I had to build a custom version of the pcmcia tools with uclibc only doing the absolute minimum to get the wireless interface up. IIRC I only had a couple of Kb left over. -- Richard A. Smith

6 15

[LinuxBIOS] VIA VT8605 support
by Joep Jansen Jan. 17, 2006

Jan. 17, 2006

I would like to port Linux BIOS to an embedded CPU board: the Kontron ETX-P3M. The board has a 400 MHz Celeron CPU, VIA VT8605 northbridge, and VIA VT82C686B southbridge. I would like to know if anybody has some experience with LinuxBIOS and these or similar chips. What would be a good starting point? Is the vt8605 similar to the (supported) vt8601? What about the vt82c686b? Thanks, Joep On Wed, Jan 11, 2006 at 12:33:26PM -0800, Adam Talbot wrote: >So I have my new embedded board. It is running a chip set that is not >supported, yet. I have all the doc's, that I think I will need. I >would like to start trying to add support for the vt8605/vt8606 based >board(s). >

2 1

[LinuxBIOS] ALi M1489 & M1487 Chipset
by kratchkov Jan. 14, 2006

Jan. 14, 2006

Hello everyone, I found a strange board (get some pictures from http://bram.dhis.org/pub/ror1000/) which has the following chips on it: - AMD AM486DX5-133 processor - ALI M1487 and ALI M1489 chipsets - BASIS Communications (ex-Cirrus Logic) CL-PD6729 PCMCIA controller with two PCMCIA slots - AMD PCnet-FAST III network controller - EPIC Ei-16C550 serial FIFO UART - with one serial connector There is no keyboard plug, no graphiccard, no PCI, no ISA. All these chips are supported by linux (to my knowledge, correct me if I'm wrong). Further, there are 4MB RAM (two GM71V18163CJ6 with 1M-words each), and 512kB FlashROM (Hy29F040AC-90; PLCC32 outline). The latter seems to be like a BIOS, including the original firmware. The board is from a ORiNOCO ROR-1000 wireless accesspoint, and works with the original firmware, but there is not much I can do with, since I do not have a pcmcia wireless card. Trying to find a way to put linux on it, I stumbled on LinuxBIOS, and wondered if it was possible to replace the firmware with it. Is the ALi chipset supported? Are there any special problems which could be encountered by using LinuxBIOS on such a small board? Thanks in advance. Greetings from switzerland, Matthias

1 0

Re: [LinuxBIOS] Compile error
by Lu, Yinghai Jan. 13, 2006

Jan. 13, 2006

http://www.batbuilds.com/webfolders/linuxbios/src/northbridge/via/vt8605 _6/northbridge.c struct chip_operations northbridge_via_vt8601_ops = { CHIP_NAME("VIA vt8601 Northbridge") .enable_dev = enable_dev, }; ===> struct chip_operations northbridge_via_vt8605_6_ops = { CHIP_NAME("VIA vt8605_6 Northbridge") .enable_dev = enable_dev, }; -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Adam Talbot Sent: Friday, January 13, 2006 6:23 PM To: linuxbios(a)openbios.org Subject: [LinuxBIOS] Compile error Still trying to build Linux bios on my new board. Have solved allot of compile errors, but this one had me stuck. "undefined reference to `northbridge_via_vt8605_6_ops`". As best I can tell this is coming from c_start.s. The only peace of code I have with that line in it is /root/LinuxBIOSv2-2158/src/northbridge/via/vt8605_6/chip.h. Here is my current tree. http://www.batbuilds.com/webfolders/linuxbios/ Any ideas? -Adam linuxbios_ram.ld linuxbios_ram.o linuxbios_ram.o: In function `write_tables': : undefined reference to `write_pirq_routing_table' linuxbios_ram.o: In function `_idt_end': /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0x9b4): undefined reference to `northbridge_via_vt8605_6_ops' /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0xc54): undefined reference to `northbridge_via_vt8605_6_ops' /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0xef4): undefined reference to `northbridge_via_vt8605_6_ops' /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0x11b4): undefined reference to `northbridge_via_vt8605_6_ops' /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0x1454): undefined reference to `northbridge_via_vt8605_6_ops' linuxbios_ram.o:/root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.dat a+0x16f4): more undefined references to `northbridge_via_vt8605_6_ops' follow collect2: ld returned 1 exit status make[1]: *** [linuxbios_ram] Error 1 make[1]: Leaving directory `/root/LinuxBIOSv2-2158/targets/bcm/ebc3610/ebc3610/normal' make: *** [normal/linuxbios.rom] Error 1 -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios

2 1

[LinuxBIOS] Compile error
by Adam Talbot Jan. 13, 2006

Jan. 13, 2006

Still trying to build Linux bios on my new board. Have solved allot of compile errors, but this one had me stuck. "undefined reference to `northbridge_via_vt8605_6_ops`". As best I can tell this is coming from c_start.s. The only peace of code I have with that line in it is /root/LinuxBIOSv2-2158/src/northbridge/via/vt8605_6/chip.h. Here is my current tree. http://www.batbuilds.com/webfolders/linuxbios/ Any ideas? -Adam linuxbios_ram.ld linuxbios_ram.o linuxbios_ram.o: In function `write_tables': : undefined reference to `write_pirq_routing_table' linuxbios_ram.o: In function `_idt_end': /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0x9b4): undefined reference to `northbridge_via_vt8605_6_ops' /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0xc54): undefined reference to `northbridge_via_vt8605_6_ops' /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0xef4): undefined reference to `northbridge_via_vt8605_6_ops' /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0x11b4): undefined reference to `northbridge_via_vt8605_6_ops' /root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0x1454): undefined reference to `northbridge_via_vt8605_6_ops' linuxbios_ram.o:/root/LinuxBIOSv2-2158/src/arch/i386/lib/c_start.S:(.data+0x16f4): more undefined references to `northbridge_via_vt8605_6_ops' follow collect2: ld returned 1 exit status make[1]: *** [linuxbios_ram] Error 1 make[1]: Leaving directory `/root/LinuxBIOSv2-2158/targets/bcm/ebc3610/ebc3610/normal' make: *** [normal/linuxbios.rom] Error 1

1 0

[LinuxBIOS] small 64bit initrd
by Lu, Yinghai Jan. 11, 2006

Jan. 11, 2006

Any progress about small size 64bit initrd? I'm using suse 91 rescure initrd, it is about 18M (gzip -9)... YH

5 9

[LinuxBIOS] The full "How to"
by Adam Talbot Jan. 11, 2006

Jan. 11, 2006

So I have my new embedded board. It is running a chip set that is not supported, yet. I have all the doc's, that I think I will need. I would like to start trying to add support for the vt8605/vt8606 based board(s). Looking for some doc's on the linuxbios web page about were to start and what files tie in to the build, and where. Can some one point me to such a doc, or can we build such a doc. What files do I need to mod/build? What order should I work on them? What kind of response should I be looking for from the console to tell me if that step is working? Stating that I can get console running I the first place, yes my superIO is supported. Is there any "How to" that covers this, or is it time to build one. -Adam

3 3

Re: [LinuxBIOS] small 64bit initrd
by Lu, Yinghai Jan. 11, 2006

Jan. 11, 2006

For LinuxBIOS support, besides mkelfImage, We still need cmos_util... We may can separate these stuff in two location 1. kernel + initrd( with busybox as shell) --- with this we can access all media. (I don't want to use udev) 2. final kernel. mkelfImage. Cmos_util.... YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Wednesday, January 11, 2006 2:02 PM To: Ronald G Minnich Cc: Lu, Yinghai; linuxbios(a)openbios.org; Fastboot mailing list; kboot-general(a)lists.sourceforge.net Subject: Re: [LinuxBIOS] small 64bit initrd Ronald G Minnich <rminnich(a)lanl.gov> writes: > Eric W. Biederman wrote: > >> Check it out just skimming through the documentation it looks like it >> has already surpassed FILO in capabilities. > > I think kboot and tinykernels and such could get us back to the original vision > of linuxbios from years ago -- linux is the bios. Let's hope. One step at a time. A lot of the tiny kernel work has been merged into linus's tree for 2.6.16. I think the interesting linuxbios related kboot activities are. 1) Hook mkelfImage into the build so we will easily have an image that we can use with linuxbios. 2) Figure out how to use kboot on host nodes :) Video now works on a good day. And then there is my very evil plan spam the kboot list on topic discussion :) Eric

1 0