coreboot

coreboot@coreboot.org

12 participants
39779 discussions

Re: Supporting extension ROMs and beyond...
by YhLu 11 Aug '03

11 Aug '03

Ron, If the user want to LinuxBIOS with embedded solution with screen (SET TOP BOX???) the VGA support must be ready and some Workstation also need that. Otherwise it will limit the application scope of linubios. Other option rom will be another story, for example: about Serial ATA, Promise doesn't want provide support, but it's OK , We can get detail info from Silicon Images chip, so We can use their solution and forget Promise. As for the scsi chip, LSI likes to share the info. So We can produce their chip support at first. ( I have add the support for LSI scsi chip). As for Adaptec is hesitating to give the detail info, and may need more request to them. It is said Only DELL have got the corresponding from them. Who will move VGABIOS support to freebios2 ? I would have a try on Tyan S2885 . (Two Opterons and workstation MB) this week. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年8月11日 8:59 收件人: Eric W. Biederman 抄送: SONE Takeshi; Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: Supporting extension ROMs and beyond... On Mon, 11 Aug 2003, ron minnich wrote: > For linuxbios to succeed in future, we'll need support for these two > things. I think this is a lamentable state of affairs. But that's how it > is. > > I think long-term the best way to fix it for all architectures is via > emulation, but for the immediate-term we can make callback/binary support > for the common(-est) case: the x86. I contradict myself. Either we need callbacks or we don't. If we get emulation, we don't need them. Sorry for my confusing note. Eric, I am sympathy with what you are saying. There is a reality here -- people want VGA and they want it on early. I want to accomodate this. Is emulation a suitable, architecture-independent way to achieve this? I'm thinking it might be. Can we then build it in as an option when we build a linuxbios? thanks ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

sc1200 (GX1)
by Brian G. Rhodes 11 Aug '03

11 Aug '03

This is not directly linuxbios related at all, but since there have been some other people asking questions about the geode gx1 hardware, I am curious. Is anyone successfully using National's fastPCI (66MHz)? The hardware I am working on seems to lock up when doing a large number or reads, or big reads. It is most evident when using DMA with IDE. Any ideas? Brian G Rhodes bgr(a)linespeed.net brhodes(a)visualcircuits.com +1 612-741-1191

1 0

VGA BIOS init debate
by Adam Agnew 11 Aug '03

11 Aug '03

I want to throw these arguments into the debate: I vote for the ELF payload. I would say that linking it in would be just as good, except that if EFI ever does really become common, a lot of these payloads would become useful to a larger user base. I do agree that there would be some redundancy in code, but I also believe the build process would be simplified (rom-o-matic certainly seems more feasible without so many options) and those new to LinuxBIOS would be able to grasp how it all links together easier. Right now, the split in idealogy has put us in quite the pickle. Linuxbios has two ways to tftp boot, three ways to polled ide boot, two ways to get a vga rom up and running.. If things are still even linked in to freebios2, there's a lot of confusion. Do different boot methods use elf payloads or are they compiled in? Well that would depend on which one. I too would like the Linux kernel to solve all of these problems, I hope I've never created the impression that I wish otherwise. But the chunk of mailing list traffic from embedded enthusiasts is getting still larger, nothing's really changed in ROM size since the Great Payload Debates of 2001, and Linux has only gotten bigger (though there's hope..). - Adam Agnew On Fri, 8 Aug 2003, ron minnich wrote: > folks, any opinions expressed on this VGA BIOS discussion would be > welcome. > > VGA BIOS in linuxbios, or in an ELF payload? What's your bet? > > ron > >

2 1

Backoirted oatch to 2.4.19 for kexec does not work
by Gregg C Levine 10 Aug '03

10 Aug '03

Hello from Gregg C Levine I don't know why, Andrew, but the patch your company supplied via the FTP site, for the 2.4.19 kernel, applied correctly, and I was able to build the kernel. But the expected event didn't work. When I issued a "kexec kernel.elf", which was built using the latest version of mkelfImage from the FTP site, that Eric has for his company, I got the same expected output as before. Here it is: Script started on Sun Aug 10 21:11:01 2003 root@drwho4:/usr/src/lobos/work# kexec kernel.elf kexec_load failed: Function not implemented entry = (nil) nr_segments = 4 segment[0].buf = 0x80a8ea0 segment[0].bufsz = 158 segment[0].mem = (nil) segment[0].memsz = 158 segment[1].buf = 0x80a3888 segment[1].bufsz = 559c segment[1].mem = 0x10000 segment[1].memsz = 1aa24 segment[2].buf = 0x80a8e28 segment[2].bufsz = 0 segment[2].mem = 0x91000 segment[2].memsz = 70 segment[3].buf = 0x40001008 segment[3].bufsz = b48dc segment[3].mem = 0x100000 segment[3].memsz = 700000 root@drwho4:/usr/src/lobos/work# exit Script done on Sun Aug 10 21:11:12 2003 Incidentally that's the same thing that I got before. Did this function work for you? What distribution did you use for building your kernel, and, ah, test system? As it happens, this is built using Slackware 8.0, with the compiler version as 2.95.3, and the binary utilities at 2.10.90. Do I need to upgrade them for attempting to build the later kernels? ------------------- Gregg C Levine hansolofalcon(a)worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )

2 3

re: S2880
by YhLu 10 Aug '03

10 Aug '03

Eric, Under 4G RAM linusbios_tables occupy 0x500-0xae0, cmos_util can find option_table even after rebooting. Under 6G RAM linuxbios_tables occupy 0x500-0xaf4, cmos_util can find option_table after power on but can not find it after rebooting. The only difference should be that rebooting don't execute auto.c again. Any advise. Regards Yingahi Lu -----邮件原件----- 发件人: YhLu 发送时间: 2003年8月6日 17:11 收件人: ron minnich 抄送: 'ebiederman(a)lnxi.com'; 'Stefan Reinauer'; 'linuxbios(a)clustermatic.org' 主题: 答复: S2880 Ron, I have verfied that if I disable the XIP... in old config tool, the image produced will make the option table not accessiable after reboot too. Regards Yinghai Lu -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年8月6日 15:51 收件人: YhLu 抄送: 'ebiederman(a)lnxi.com'; 'Stefan Reinauer'; 'linuxbios(a)clustermatic.org' 主题: Re: S2880 I will try to email you my latest tree, Stefan put them in last night. ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

8 13

Preliminary doubts
by John Praveen 10 Aug '03

10 Aug '03

Hi, I have the custom board (geode sc1200) with some external peripherals. I will have to have my BIOS program, linux kernel and specific application program in my Flash memory. I have hard disk only for storing files. My Flash memory is of 32 Mbits and SDRAM 32MBytes. I want to use LinuxBios. I build it for nano mainboard. But still I have many doubts. In normal BIOS, we will say the bios program to load the bootloader from hard disk into location 0000:7C00. What part of the program in Linuxbios will bring my linux kernel image from Flash into SDRAM? Is any options or something to be included in the configuration file to say to boot from Flash memory? In my embedded device the Flash memory is mapped to physical address 00000h to 3FFFFFh. So at what location should i place the linuxbios romimage and linux kernel image in my Flash memory? Where shall my application program be placed in Flash? I hope I should have a filesystem. Is the MTD meant for the filesystem? Please help me. Thanks in advance. Regards, John. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

3 2

help can't get it working on epia-m10000
by James Weir 10 Aug '03

10 Aug '03

I have included below the output from the console when attempting to boot linuxbios, it always seems to just hang at this point... any pointers... I am on an EPIA-M10000 board. Thanks, James. LinuxBIOS-1.0.0 Sun Aug 10 17:10:40 BST 2003 starting... Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.0.0 Sun Aug 10 17:10:40 BST 2003 booting... 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: 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 <- [0xfeb00000 - 0xfeb007ff] mem PCI: 00:0d.0 14 <- [0x00001800 - 0x0000187f] io PCI: 00:10.0 20 <- [0x00001880 - 0x0000189f] io PCI: 00:10.1 20 <- [0x000018a0 - 0x000018bf] io PCI: 00:10.2 20 <- [0x000018c0 - 0x000018df] io PCI: 00:10.3 10 <- [0xfeb01000 - 0xfeb010ff] mem PCI: 00:11.1 20 <- [0x000018e0 - 0x000018ef] io PCI: 00:11.5 10 <- [0x00001000 - 0x000010ff] io PCI: 00:12.0 10 <- [0x00001400 - 0x000014ff] io PCI: 00:12.0 14 <- [0xfeb02000 - 0xfeb020ff] 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 done. Initializing PCI devices... PCI devices initialized totalram: 127M Initializing CPU #0 Enabling cache... Setting fixed MTRRs(0-88) type: UC

3 3

Problem with EPIA-M10000
by James Weir 10 Aug '03

10 Aug '03

I have narrowed the problem to a hang at the disable_cache() call in mtrr.c file in cpu/p6 directory of the src tree. It is also worth noting that the board has 256Mb installed not 127Mb as it suggests in debug output ( see previous post ). James :-)

1 0

Gigabyte BX2000
by Michael Schuele 09 Aug '03

09 Aug '03

Hi, I've got a Gigabyte BX2000 mainboard with an Intel BX chipset. It has a so called "dual bios" which means that there is a backup bios from which you can recover your "main" bios if flashing failed or something other happend to it. Do you know if I can use LinuxBios on this board or should I try to get an other board? Which kernel patch do I have to use? I can't find one in src/kernel-patches.. I downloaded the kernel from cwlinux.com, is this already patched or what is it for? thx, Michael

1 0

EPIA-ME6000
by Leon Woestenberg 09 Aug '03

09 Aug '03

Hello, I have been fiddling with etherboot 5.0.10 and freebios(v1) from CVS today on a EPIA-ME6000 platform. This is the unit with a low speed clock (500MHz?) Eden C3 processor which copes with passive cooling. I think it is EPIA-M9000 alike otherwise. Using a hardware flash programmer, I first copied the VIA BIOS from the STT39SF040A (256Kbytes) into a STMicro 29F040B (512Kbytes) device. That only worked after I copied the BIOS into the upper half of the larger device (from 0x40000 to 0x7FFFF). So I recon the highest address line is not connected on the board and so the FlashROM sees high-impedance on its most significant address line (and addresses the upper half always)> I followed the HOWTO/EPIA document to the letter (without the VGA BIOS at first) booting linuxbios w/ via-rhine.elf payload. When booting, I merely got garbled output on the serial port. I have double checked that the config file reads 115200 and that my terminal reads 115200 8N1. (The 115200 is assembly hardcoded in the vt82c686 superio code -- does it cope with my different processor speed? I do not have the datasheet (yet?). After that, I have tried all speeds on the terminal without result. Is the EPIA-ME6000 (aka M6000) already reported to work here, or are you guys'n'gals refering to the M9000 and M10000 alone? How can I help? Regards, Leon.

6 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot