coreboot November 2004

coreboot@coreboot.org

31 participants
183 discussions

xen,bproc and grub
by Adam Sulmicki 07 Nov '04

07 Nov '04

Hello, I have recently ported bproc [1] which part of clustermatic [2] suite to xen-2.0 [3] to run on domain0. It was pretty straightforward, that it required few trival hacks to the kernel, few sym-links and remembering to use "ARCH=xen" whenever appropriate. However, clustermatic does use linuxbios on its nodes for booting and does not use traditional bios at all. This means that the grub (with its multiboot support) with its heavy dependencies on PC-BIOS Is out of window. Thus I'm trying to figure out how I could boot xen/linux-2.6.8.1-xen0 duo on nodes. Are there any other options to boot it besides using grub[4][5]? and preferably does not rquire multiboot [6]. I figure out I that maybe could load xen.gz [7] using FILO, Kexec, or maybe etherboot but it still would not load linux kernel in turn (because of the dependency on multiboot). Anyone knows what are my options here? Ideas? [1] http://bproc.sourceforge.net/ [2] http://www.clustermatic.org/ [3] http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ [4] grub configuration file entry for xen title Xen 2.0 / XenLinux 2.6.8.1 kernel (hd0,0)/boot/xen.gz dom0_mem=65536 module (hd0,0)/boot/vmlinuz-2.6.8.1-xen0 root=/dev/hda1 [5] grub-multiboot, from info page - Command: module file ... Load a boot module FILE for a Multiboot format boot image (no interpretation of the file contents are made, so the user of this command must know what the kernel in question expects). The rest of the line is passed as the "module command-line", like the `kernel' command. You must load a Multiboot kernel image before loading any module. See also *Note modulenounzip::. [6] http://www.gnu.org/software/grub/manual/multiboot/multiboot.html does anyone knows better references to multiboot specs? [7] /boot/xen.gz redbull:/etc/clustermatic # file /boot/xen.gz /boot/xen.gz: gzip compressed data, from Unix, max compression redbull:/etc/clustermatic # file /tmp/xen /tmp/xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped redbull:/etc/clustermatic # readelf -a /tmp/xen ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x100000 Start of program headers: 52 (bytes into file) Start of section headers: 266608 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 1 Size of section headers: 40 (bytes) Number of section headers: 3 Section header string table index: 2 Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [ 0] NULL 00000000 000000 000000 00 0 0 0 [ 1] .text PROGBITS 00100000 000080 0410f0 00 WAX 0 0 64 [ 2] .shstrtab STRTAB 00000000 0411e8 000011 00 0 0 1 Key to Flags: W (write), A (alloc), X (execute), M (merge), S (strings) I (info), L (link order), G (group), x (unknown) O (extra OS processing required) o (OS specific), p (processor specific) Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x000080 0x00100000 0x00100000 0x410f0 0x764c0 RWE 0x40 Section to Segment mapping: Segment Sections... 00 .text There is no dynamic segment in this file. There are no relocations in this file. There are no unwind sections in this file. No version information found in this file. redbull:/etc/clustermatic #

1 1

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

1. root_complex pci_domain NB SB End End Apic End Is more understanding even for one MC MB. 2. Without " config chip.h" The corresponding device chip_ops field will be 0, and not to some ......ops (all zero). 3. another is if not define " uses CONFIG_CHIP_NAME" in MB Option.lb and use "if CONFIG_CHIP_NAME config chip.h end the config.g will be report CONFIG_CHIP_NAME is not defined, just some other strang reporting. Regards YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Friday, November 05, 2004 5:13 PM To: YhLu Cc: 'Ronald G. Minnich'; 'Li-Ta Lo'; 'LinuxBIOS' Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > I changed e7501 to use root_complex too. Could we please reserve this construct for chipsets with multiple northbridges? I think it is just going to be extra noise on a simple chipset like the e7501. And since the e7501 is an example to a certain extent having it doing extra work be confusing and a pain. > If the chip_ops has no .name, then should use > if CONFIG_CHIP_NAME > config chip.h > end > > also .c include that chip_ops > #if CONFIG_CHIP_NAME > ...chip_ops defininition > #endif > > Regards > > Such as norththbridge, socket, mainboard(root). They can. But I am about to suggest simply removing the config directive, and assuming the ``config chip.h'' is always given. The overhead is almost zero for a zero filled structure. And always requiring a chip.h would tend to simply the process of writing code for a new chip. Eric

1 0

Re: [Freebios-cvs] freebios2/util/abuild abuild.sh,1.5,1.6
by Stefan Reinauer 05 Nov '04

05 Nov '04

Eric, I tried this before as well, but it does not work, at least with my util-linux 2.11z: ./abuild.sh -h LBROOT=-h ls: invalid option -- / Try `ls --help' for more information. Which is why I ended up doing the workaround I used. Do you know a fix that actually helps fixing your fix, or shall I revert your changes? Stefan * Eric Biederman <ebiederm(a)users.sourceforge.net> [041105 09:50]: > Index: abuild.sh > =================================================================== > RCS file: /cvsroot/freebios/freebios2/util/abuild/abuild.sh,v > retrieving revision 1.5 > retrieving revision 1.6 > diff -C2 -d -r1.5 -r1.6 > *** abuild.sh 5 Nov 2004 00:26:31 -0000 1.5 > --- abuild.sh 5 Nov 2004 08:50:53 -0000 1.6 > *************** > *** 254,258 **** > > # parse parameters > ! args=`getopt -l version,verbose,help,all,target: Vvhat: $*` > > if [ $? != 0 ]; then > --- 255,259 ---- > > # parse parameters > ! args=`getopt -l version,verbose,help,all,target: Vvhat: -- "$@"` > > if [ $? != 0 ]; then > *************** > *** 261,278 **** > fi > > ! set -- $args > ! for arg > ! do > ! case $arg in > ! -t|--target) shift;target=$1;shift;; > ! -a|--all) shift;buildall=true;; > ! -v|--verbose) shift;verbose=true;; > ! -V|--version) shift;myversion;; > ! -h|--help) shift;myhelp;; > ! esac > done > > ! # -- is $1 > ! LBROOT=$2 > > # /path/to/freebios2/ > --- 262,279 ---- > fi > > ! eval set -- "$args" > ! while true ; do > ! case $1 in > ! -t|--target) shift; target=$1; shift;; > ! -a|--all) shift; buildall=true;; > ! -v|--verbose) shift; verbose=true;; > ! -V|--version) shift; myversion;; > ! -h|--help) shift; myhelp;; > ! --) shift; break;; > ! *) echo "Unrecognized argument" ; exit 1 ;; > ! esac > done > > ! LBROOT=$1 > > # /path/to/freebios2/ > *************** > *** 280,283 **** > --- 281,285 ---- > LBROOT=$( cd ../..; pwd ) > fi > + echo "LBROOT=$LBROOT" > > if [ "$target" != "" ]; then

3 7

RE: PCI_DOMAIN ??
by YhLu 05 Nov '04

05 Nov '04

Create dummy device, and assign devfn to it, then.... YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Wednesday, November 03, 2004 2:59 PM To: Eric W. Biederman Cc: LinuxBIOS Subject: Re: PCI_DOMAIN ?? On Wed, 2004-11-03 at 15:51, Eric W. Biederman wrote: > So my immediate suggestion would be to call pci_set_method from the pci_domain's > scan_bus method before it does anything. We can worry about the rest later. > Isn't the root_dev::scan_bus() called before pci_domain::scan_bus() ? What if root_dev::scan_bus() wants to access PCI CS ? Ollie _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

Eric, If the chip_ops has no .name, then should use if CONFIG_CHIP_NAME config chip.h end also .c include that chip_ops #if CONFIG_CHIP_NAME ...chip_ops defininition #endif Regards Such as norththbridge, socket, mainboard(root). YH -----Original Message----- From: YhLu Sent: Friday, November 05, 2004 10:50 AM To: ebiederman(a)lnxi.com Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? What does "config chip.h" in Config.lb use for? It seems it is not necessary? Regards YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Friday, November 05, 2004 10:31 AM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > Forget about that. Ok. > Why separate root_complex from amdk8/northbridge.c to > root_complex/root_complex.c I haven't because the code is to intertwined in northbridge.c and it would be likely be a maintenance problem to do so. Eric _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

Static.c include comes from it. YH -----Original Message----- From: YhLu Sent: Friday, November 05, 2004 10:44 AM To: 'ebiederman(a)lnxi.com' Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? What does "config chip.h" in Config.lb use for? It seems it is not necessary? Regards YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Friday, November 05, 2004 10:31 AM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > Forget about that. Ok. > Why separate root_complex from amdk8/northbridge.c to > root_complex/root_complex.c I haven't because the code is to intertwined in northbridge.c and it would be likely be a maintenance problem to do so. Eric

1 0

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

What does "config chip.h" in Config.lb use for? It seems it is not necessary? Regards YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Friday, November 05, 2004 10:31 AM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > Forget about that. Ok. > Why separate root_complex from amdk8/northbridge.c to > root_complex/root_complex.c I haven't because the code is to intertwined in northbridge.c and it would be likely be a maintenance problem to do so. Eric

1 0

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

Forget about that. Why separate root_complex from amdk8/northbridge.c to root_complex/root_complex.c YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Thursday, November 04, 2004 8:53 PM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > No, debug_dev can be PCI_DOMAIN and APIC's sibling and one child dev_root in > link0. So why the question about dev_root link 1 and 2? Eric

2 1

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

Share get_fx_devs and f1_read_config32? YH -----Original Message----- From: YhLu Sent: Friday, November 05, 2004 10:17 AM To: ebiederman(a)lnxi.com Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? Forget about that. Why separate root_complex from amdk8/northbridge.c to root_complex/root_complex.c YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Thursday, November 04, 2004 8:53 PM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > No, debug_dev can be PCI_DOMAIN and APIC's sibling and one child dev_root in > link0. So why the question about dev_root link 1 and 2? Eric _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

8131 and 8151 in static.c
by Li-Ta Lo 05 Nov '04

05 Nov '04

Eric, Why there is no struct southbridge_amd_amd8131_config or struct southbridge_amd_amd8151_config in ter static.c although we have chip southbridge/amd/amd8131 and chip southbridge/amd/amd8151 in the Config.lb? There is no struct chip_operations southbridge_amd_amd8131_ops nor struct chip_operations southbridge_amd_amd8151_ops nether. Ollie

3 2

← Newer
1
...
8
9
10
11
12
13
14
...
19
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 November 2004