coreboot

coreboot@coreboot.org

6 participants
39707 discussions

Re:debugger
by jarcher 15 May '03

15 May '03

That may work. Longer term I'm more worried about debugging payloads. As they will probably change more often than the prebios stuff. Jordan At 01:55 PM 5/15/2003 -0400, steven james wrote: >On Thu, 15 May 2003, jarcher wrote: > > > PS: Has anyone done a USB interface low level debugger? Early BIOS or at > > least just prior to payload decompress. > >I've looked into it, but it's a bit complex to have up at that point (at >least with the regular UHCI and OHCI). At the least, it will require RAM >and a portion of PCI to be up and running. At that point, might as well >just put it in the C code after PCI init. > >G'day, >sjames > > >-- >-------------------------steven james, director of research, linux labs >... ........ ..... .... 230 peachtree st nw ste 2701 >the original linux labs atlanta.ga.us 30303 > -since 1995 http://www.linuxlabs.com > office 404.577.7747 fax 404.577.7743 >-----------------------------------------------------------------------

1 0

Intel L440GX+
by Jonathan B. Horen 15 May '03

15 May '03

Shalom! While reading the LinuxBIOS website FAQ, I looked for instructions for building the romimage for the Intel L440GX+ motherboard -- they're missing; I also tried the link for Intel's "System Update Package" -- it's a dead link. So, can anyone send me build instructions for my motherboard and a pointer to the SUP? TIA! (33-node Beowulf cluster, wanting to move to LinuxBIOS/BeoBOOT/BProc) -- JONATHAN B. HOREN UNIX SYSTEMS ADMINISTRATOR E: horen(a)mail.iucc.ac.il Inter-University Computation Center T: +972-(0)3-640-5203 Tel-Aviv University F: +972-(0)3-640-9118 Ramat-Aviv 69978 Israel

2 1

EPIA VGA patch
by SONE Takeshi 15 May '03

15 May '03

Hello, I started with a fresh checkout of CVS tree (since my current working tree is a mess) and made a minimum modification to boot ADLO with VGA BIOS to enable video on a EPIA. With attached patches, my EPIA 5000 boots into GRUB (then Linux) with VGA console. lb-epia.patch This applies to LinuxBIOS itself. Enables shadow RAM, adds vgainit.inc (it is harmless unless HAVE_FRAMEBUFFER is enabled), and a minimum fix to raminit.inc. Ron, please apply this one. adlo-epia.patch This is for ADLO. Since it includes changes specific to EPIA, it should not (entirely) go into CVS. Note that this includes serial debug patch by hcyun, and EPIA doesn't work without it. Perhaps a timing problem? pirq-EPIA.bin This should be put at util/ADLO/pirq. It was taken from LinuxBIOS, not Award BIOS (I think it makes sense). Of cource, VGA BIOS is also required and it must be taken from your box. As I said this is minimum modification, it does not boot very fast, and it may fail to detect IDE at cold boot. For these issues, I have already posted fixes to the list. RAM is fixed at 64MB, as current CVS is. If you change this, you have to hack raminit.inc, as well as CMOS value in the ADLO/loader.s. I'm working on automatic detection of RAM. Have fun. -- Takeshi

4 6

RE: TUSL2-C almost work.....
by Yap Ee Huey 15 May '03

15 May '03

Hi, I thought zkernel_start could be the reason, but not : --------------------------------------------------------------------------- Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 203:init_bytes() - zkernel_start:0xfffc0000 zkernel_mask:0x0000007f Searching for 16 byte tags 64:rom_read_bytes() - overflowed source buffer. max_block = 3 init_bytes found 0 tags Found ELF candiate at offset 0 Loading Etherboot version: 5.1.8 Dropping non PT_LOAD segment New segment addr 0x20000 size 0x12e0f offset 0xb0 filesize 0x3f5d (cleaned up) New segment addr 0x20000 size 0x12e0f offset 0xb0 filesize 0x3f5d Loading Segment: addr: 0x000000000ff7ec68 memsz: 0x0000000000012e0f filesz: 0x0000000000003f5d Clearing Segment: addr: 0x000000000ff82bc5 memsz: 0x000000000000eeb2 Jumping to boot code at 0x20000 (Restarted) LinuxBIOS-1.0.0 Tue May 13 11:51:30 EDT 2003 starting... Ram1 Ram2 ................. --------------------------------------------------------------------------- Still looping............ My kernel was built by : mkelfImage --command-line="root=/dev/hda5 console=ttyS0,19200" --kernel vmlinux -o vmlinux..elf But the ELF image cannot be tagged. (invalid linux kernel) Also, the tagged bzImage cannot be made ELF. (Not an linux kernel at line 73) Could it be a problem ? I should have a tagged ELF according to the Documentation. Thanks a lot. regards, eehuey >From: hcyun(a)etri.re.kr >To: yapeehuey(a)hotmail.com, rminnich(a)lanl.gov >CC: linuxbios(a)clustermatic.org >Subject: RE: TUSL2-C almost work..... >Date: Thu, 15 May 2003 15:28:14 +0900 > > > > Welcome to elfboot, the open sourced starter. > > January 2002, Eric Biederman. > > Version 1.2 > > 203:init_bytes() - zkernel_start:0xfff00000 > > zkernel_mask:0x0000ffff > > Searching for 16 byte tags > > 64:rom_read_bytes() - overflowed source buffer. max_block = 15 > > init_bytes found 0 tags > > Found ELF candiate at offset 0 > > Loading Etherboot version: 5.1.8 > > Dropping non PT_LOAD segment > > New segment addr 0x20000 size 0xeee0 offset 0xb0 filesize 0x617c > > (cleaned up) New segment addr 0x20000 size 0xeee0 offset 0xb0 > > filesize > > 0x617c > > Loading Segment: addr: 0x000000000ff7ece8 memsz: > > 0x000000000000eee0 filesz: > > 0x000000000000617c > > Clearing Segment: addr: 0x000000000ff84e64 memsz: 0x0000000000008d64 > > Jumping to boot code at 0x20000 > > -------------------------------------------------------------- > > ---------------------------------------------- > > > > Then it restarts. > >It seems like you should specify ZKERNEL_START correctly. If you have 256KB >flash part, ZKERNEL_START should be 0xfffc0000. > >Heechul. > _________________________________________________________________ Download the latest MSN Messenger http://messenger.msn.com.my

2 1

RE: TUSL2-C almost work.....
by hcyun＠etri.re.kr 15 May '03

15 May '03

> Welcome to elfboot, the open sourced starter. > January 2002, Eric Biederman. > Version 1.2 > 203:init_bytes() - zkernel_start:0xfff00000 > zkernel_mask:0x0000ffff > Searching for 16 byte tags > 64:rom_read_bytes() - overflowed source buffer. max_block = 15 > init_bytes found 0 tags > Found ELF candiate at offset 0 > Loading Etherboot version: 5.1.8 > Dropping non PT_LOAD segment > New segment addr 0x20000 size 0xeee0 offset 0xb0 filesize 0x617c > (cleaned up) New segment addr 0x20000 size 0xeee0 offset 0xb0 > filesize > 0x617c > Loading Segment: addr: 0x000000000ff7ece8 memsz: > 0x000000000000eee0 filesz: > 0x000000000000617c > Clearing Segment: addr: 0x000000000ff84e64 memsz: 0x0000000000008d64 > Jumping to boot code at 0x20000 > -------------------------------------------------------------- > ---------------------------------------------- > > Then it restarts. It seems like you should specify ZKERNEL_START correctly. If you have 256KB flash part, ZKERNEL_START should be 0xfffc0000. Heechul.

1 0

cvs co error
by Frank 14 May '03

14 May '03

I am getting the following error when trying to co linuxbios for the first time: cvs [checkout aborted]: could not chdir to freebios/src/arch/alpha/config: Not a directory anyone have an idea as to what is going on... __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

7 12

Re: cvs co error
by Richard Smith 14 May '03

14 May '03

Frank wrote: > It looks like cvs under cygwin is the culprit. Anyone know how > to resolve this... I don't think there is a solution currently for use on a non-case sensitive filesystem. > --- Richard Smith <rsmith(a)bitworks.com> wrote: > >>>I am getting the following error when trying to co linuxbios >>>the first time: >>>cvs [checkout aborted]: could not chdir to >>>freebios/src/arch/alpha/config: Not a directory >> >>Do you per chance have that on a filesystem that isn't case >>sensitive? >>In the alpha directory there is both a 'Config' file and a >>'config' >>directory. -- Richard A. Smith rsmith(a)bitworks.com

1 0

RFC:new superio proposal
by ron minnich 14 May '03

14 May '03

Abstract: The superio architecture for linuxbios has worked for the last 2 years but is being stretched to the limit by the changes in superio chips. The architecture depended on superio resources being relatively constant between chips, but this assumption no longer holds. In this document we propose several alternatives and solicit comments. Overview: The superio architecture in linuxbios was developed over time, and modified as circumstances required. In the beginning it was relatively simple and assumed only one superio per mainboard. The latest version allows an arbitrary number of superios per mainboard, and allows complete specification of the superio base I/O address along with the specification of reasonable default valures for both the base I/O address and the superio parameters such as serial enable, baud rate, and so on. Specification of superio control parameters is done by a configuration line such as: nsuperio sis/950 com1={1} floppy=1 lpt=1 This fragment sets the superio type to sis/950; sets com1, floppy, and lpt to enabled; and leaves the defaults to com1 (baud rate, etc.) to the default values. While it is not obvious, these configuration parameters are fragments of a C initializer. The initializers are used to build a statically initialized structure of this type: struct superio { struct superio_control *super; // the ops for the device. unsigned int port; // if non-zero, overrides the default port // com ports. This is not done as an array (yet). // We think it's easier to set up from python if it is not an // array. struct com_ports com1, com2, com3, com4; // DMA, if it exists. struct lpt_ports lpt1, lpt2; /* flags for each device type. Unsigned int. */ // low order bit ALWAYS means enable. Next bit means to enable // LPT is in transition, so we leave this here for the moment. // The winbond chips really stretched the way this works. // so many functions! unsigned int ide, floppy, lpt; unsigned int keyboard, cir, game; unsigned int gpio1, gpio2, gpio3; unsigned int acpi,hwmonitor; }; These structures are, in turn, created and statically initialized by a config-tool-generated structure that defines all the superios. This file is called nsuperio.c, is created for each mainboard you build, only appears in the build directory, and looks like this: === extern struct superio_control superio_winbond_w83627hf_control; struct superio superio_winbond_w83627hf= { &superio_winbond_w83627hf_control, .com1={1}, .com2={1}, .floppy=1, .lpt=1, .keyboard=1, .hwmonitor=1}; struct superio *all_superio[] = {&superio_winbond_w83627hf, }; unsigned long nsuperio = 1; === This example shows a board with one superio (nsuperio). The superio consists of a winbond w83627hf, with com1, com2, floppy, lpt, keyboard, and hwmonitor enabled. Note that this structure also allows for over-riding the default superio base, although that capability is rarely used. The control structure is used to define how to access the superio for purposes of control. It looks like this: === struct superio_control { void (*pre_pci_init)(struct superio *s); void (*init)(struct superio *s); void (*finishup)(struct superio *s); unsigned int defaultport; /* the defaultport. Can be overridden * by commands in config */ // This is the print name for debugging char *name; }; === There are three methods for stages of hardwaremain. First is pre_pci_init (for chips like the acer southbridge that require you to enable some resources BEFORE pci scan); init, called during the 'middle' phase of hardwaremain; and finishup, called before the payload is loaded. This approach was inspired by and borrows heavily on the Plan 9 kernel configuration tools. The problem: When the first version of the superio structure came out it was much smaller. It has grown and in the limit this structure is the union of all possibly superio chips. Obviously, in the long term, this is not practical: we can not anticipate all possible superio chips for all time. The common PC BIOS solution to this type of problem is to continue with binary structures but add version numbers to them, so that all code that uses a given structure has to check the version number. Personally, I find this grotesque and would rather not work this way. Using textual strings for configuration is something I find far more attractive. Plan 9 has shown that this approach has no real limits and suffices for configuration tasks. The Linux kernel does more limited use of strings for configuration, but still depends on them. Strings are easier to read and work with than binary structures, and more important, a lot easier to deal with when things start going wrong. The proposed solution: What follows are three possible ideas for specifying superio resources and their settings. A common part of the new idea is to eliminate the common superio structure, due to the many variations in chips, and make it invisible outside a given superio source file -- the superio structure is now private to a given superio. Thus, sis/950/superio.c would contain its own superio structure definitions, and also might contain more than once instance of these structures (consider a board with 2 sis 950 chips). The control structure would change as follows: struct superio_control { int (*create)(struct superio *s); void (*pre_pci_init)(struct superio *s); void (*init)(struct superio *s); void (*finishup)(struct superio *s); unsigned int defaultport; /* the defaultport. Can be overridden * by commands in config */ // This is the print name for debugging char *name; }; I.e. we add a new function for creating the superio. Communication of superio settings from linuxbios to the superio would be via textual strings. The superio structure becomes this: struct superio { struct superio_control *super; // the ops for the device. unsigned int port; // if non-zero, overrides the default port struct configuration *config; }; So now the question becomes, what is the configuration structure? There are several choices. The simplest, from my point of view, are keyword-value pairs: struct configuration { const char *keyword; const char *value; }; These get filled in by the config tool as before. The linuxbios libary can then provide a generic parsing function for the superios to use. The remaining question is how should the superio command look in freebios2? superio sis/950 "com1=115200,8n1 lpt=1 com2=9600" or superio sis/950 "com1baud=115200 lpt=1 com1chars=8n1" or superio sis/950 ((com1 115200 8n1) (lpt 1)) So, my questions: 1. Does this new scheme look workable. If not, what needs to change? 2. What should the 'struct configuration' be? does keyword/value work? 3. what should the superio command look like? Comments welcome. I'd like to adopt this "RFC" approach for freebios2 as much as we can. There was a lot of give-and-take in the early days of linuxbios about structure and it proved useful. There's a lot that will start happening in freebios2 now, and we need to try to make sure it will work for everyone. Those of you who are doing mainboards, please look at freebios2 and see how it looks for you. There's a lot of good work that has been done (not by me so far, thanks Eric and Stefan), and more that needs to be done. Consider trying out romcc as an "assembly code killer". See how it fits together and if you can work with it or need changes. Bring comments back to this list. thanks ron

6 13

hello
by Serafino Sorrenti 14 May '03

14 May '03

Hello Richard, i'm very crazy for this problem, i have done the modify at the config file for etherboot but i don't see any log in to serial port, and i don't see the linuxbios status. Tnx any more Serafino

2 1

Re: TUSL2-C almost work.....
by Yap Ee Huey 14 May '03

14 May '03

> > This has to be seek=1, not skip=1. Otherwise you overwrite your > > partition table with an incomplete elf file instead of leaving > > your partition table there and writing the complete file. > > > >I am going to regret that particular typo of mine for a long time. > >Sorry. Doesn't matter, both not working for me. I follow Richard's etherboot instructions on etherboot 5.1.8 but still no luck. Could it be my IDE harddisk not recognized ? OUTPUTS: ------------------------------------------------------------------------------------------------------ Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 203:init_bytes() - zkernel_start:0xfff00000 zkernel_mask:0x0000ffff Searching for 16 byte tags 64:rom_read_bytes() - overflowed source buffer. max_block = 15 init_bytes found 0 tags Found ELF candiate at offset 0 Loading Etherboot version: 5.1.8 Dropping non PT_LOAD segment New segment addr 0x20000 size 0xeee0 offset 0xb0 filesize 0x617c (cleaned up) New segment addr 0x20000 size 0xeee0 offset 0xb0 filesize 0x617c Loading Segment: addr: 0x000000000ff7ece8 memsz: 0x000000000000eee0 filesz: 0x000000000000617c Clearing Segment: addr: 0x000000000ff84e64 memsz: 0x0000000000008d64 Jumping to boot code at 0x20000 ------------------------------------------------------------------------------------------------------------ Then it restarts. > >I think the solution of using sfdisk to build a /dev/hda1 that starts at >sector 1 is better. Fixing etherboot to scan 64k in each direction is >best. I tried that but it still didn't find the elfimage. > >ron > _________________________________________________________________ Download ringtones, logos and picture messages from MSN Malaysia http://www.msn.com.my/mobile/ringtones/default.asp

2 1

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