coreboot

coreboot@coreboot.org

6 participants
39707 discussions

What bootloader is used?
by John Praveen 30 Jul '03

30 Jul '03

I suppose that linuxbiosmain.c is the program that loads the kernel. Is any bootloader used when booting linux from Flash memory into SDRAM? --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software

1 0

Re: EPIA-ME6000
by Brian G. Rhodes 30 Jul '03

30 Jul '03

That looks like an EPIA M-10000 compatable board to me. btw, about flash parts, you might more easily find the sst29f040 parts. also macronix makes compatable parts. You're lucky it's not a vt82c686b south as linuxbios does not work very well with that chipset. Brian G Rhodes bgr(a)linespeed.net brhodes(a)visualcircuits.com +1 612-741-1191 On Wed, 30 Jul 2003, Leon Woestenberg wrote: > Hello, > > > That board has a VIA vt82c686b south on it? I built linuxbios for a > > similar VIA board (endat) with an 8601 north and vt82c686b south. That > > > Whoops, the heatsinked chip doesn't have the vt82c686 designator, instead > it reads CLE266. You might be right in me setting up the wrong chip there. > > Let me just list the chips I can find on the board, just to make sure that > this > EPIA-EM6000 is like the M9000 board, before we head of in a wrong > direction. > > VT1211 > VT1622 > VT6103 > VT6307S > VT8235 > CLE266 (under the heatsink, next to the processor) > > Regards, > > Leon. >

1 0

size of linuxbios
by paul 29 Jul '03

29 Jul '03

Hi How big is linuxbios? will 256K byte of flash do? I only have a flash burner that will burn 512k byte. I need to know before I download the source. Thanks

3 2

Above 4G RAM
by YhLu 28 Jul '03

28 Jul '03

Eric, I have tried following memconfig on Tyan S2880. It seems ok. 4*1G DDR in CPU0 Memory slots. 2*256M DDR in CPU1 Memory slots. The MB can boot into the end. (Till end). If I use all 1G DDR, It can download the image but can not execute it and reboot again. Any advise? Regards Yinghai Lu

1 0

Re: K8 + 2.4.21 + Tyan S2880
by YhLu 28 Jul '03

28 Jul '03

Eric, My boss has said that I can release the source code to you. Please find out the patch I made. Make the diff to today's tree. I didn't test RON new script and still use the old scripts tools. I strip out the LSI scsi support, because I don't know if there is any license problem, and I have referred to their documents and may need put their FW in the ROM. It's greater you add ops->enable function that make it easy to handle special device. To some device if it is not gotten magic code, it will not get the resource allocate to it. Before that I have to do it in init function and re-allocate the resource to it again. Please refer to my old amd8131_ioapic.c in southbridge/amd8111. Also you init the io_base, upper16 reg, otherwise the device in PCIX will not got io port allocated to them, and will not work. I have tested Stefan's the code about coherent_ht.c, and add some hardcode to it. coherent_ht.o.c is the original one. Coherent_ht.1.c is total hardcode one. coherent_ht.c and coherent_ht.2.c are modified with some hardcode ones. raminit.c and raminit.1.c are till the hardcode one, and I have tried to use the configurable one, but auto.c can not be compiled, it is too big and used up REG? The old one has been renamed to raminit.o.c. To start other cpus, in auto.c We must enable apic and make sure all apic_id is right. Please refer to mainboard/tyan/s2880/auto.c boot_cpu function. Again, thank you all to answer my questions to help Tyan s2880 work with LinuxBIOS. Regards Yinghai Lu

6 13

static initialization
by Greg Watson 28 Jul '03

28 Jul '03

Stefan, I've added the ability to name parts. This means that you can do the following: cpu k8 "cpu0" register "south" = "&sb0" register "east" = "&cpu1" end cpu k8 "cpu1" register "south" = ... register "east" = ... end southbridge <device>/<vendor> "sb0" end In the k8 directory you will need to add 'config chip.h' to Config.lb, then create a chip.h that contains something like: #ifndef _CPU_K8 #define _CPU_K8 extern struct chip_control cpu_k8_control; struct cpu_k8_config { struct chip *south; struct chip *east; <any other stuff> }; #endif /* _CPU_K8 */ Then add an object that contains the code that deals with 'cpu_k8_control' (see superio/NSC/pc97307/superio.c for an example). Hopefully this will allow you to deal with the hyperchannel setup stuff. Things that still need to be done/other changes: 1. The above scheme assumes that all cpu's actually exist, which may not be the case. Only the first cpu can be relied on to exist. So we need to think about the best way to indicate that subsequent cpu's are optional. One way might be to add the keyword 'optional' to the definition. e.g. cpu k8 "cpu1" optional register "south" = ... register "east" = ... end We could add an extra pass to the chip_configure() routine called CHIP_PASS_PROBE that is called for all devices that are marked optional. It would then be up to the individual device to check for its existence. This could set a flag that means the enable() entry point is called on subsequent passes for the device. One problem with this approach is that you've already set the 'south' field to point at cpu1. If cpu1 doesn't exist then the probe code would need to set this field to 0. Let me know what you think. 2. Ron is testing replacing: cpu p5 end cpu p6 end cpu k7 end cpu k8 end with just 'cpu k8 end', then using the 'dir' command in the k8 Config.lb file to include support for k7, p6, p5. This will hopefully prevent spurious devices from being included in the static tree. 3. You now must declare: extern struct chip_control part_vendor_device_control; in the part specific chip.h file. Cheers, Greg

1 0

Epia-M
by Stefan Reinauer 28 Jul '03

28 Jul '03

* Thomas Wehrspann <thomas(a)wehrspann.de> [030727 20:10]: > is seems that the support for the ecs k7sem got broken. > When i use the current CVS copiling is no problem, but when i boot > linuxbios stops before the mtrr stuff with "Enabling cache...". I have a similar problem with the EPIA-M (latest CVS): Initializing PCI devices... PCI devices initialized totalram: 127M Initializing CPU #0 Enabling cache... Setting fixed MTRRs(0-88) type: UC [hang] Is this due to the 128MB stick I am using? It seems to get recognized though. Stefan

2 3

Mini-ITX
by John Hearns 28 Jul '03

28 Jul '03

I've been off the linuxbios list for some time. I see there are a few threads on mini-ITX. Can I ask for some pointers to ROM images for EPIA-800 and M10000 Nehemiah boards (I've just got one on order) I see the ones on cwlinux.com - which specific boards are these for? Thanks!

2 1

Linuxbios and Via M10000, where to start?
by Barbini Uberto 28 Jul '03

28 Jul '03

Hi, I'm sorry for the quite trivial question, but I cannot be able to found it by myself. I have a via M10000 motherboard and I'm using it with gentoo with kernel 2.6.0.test1 and xfree86 latest snap, and acpid for clean poweroff by power button. All works fine, and I'm quite an happy user. I'm wondering if I happiness can grow still more using linuxbios to cut off booting time. ;) But is there any risk I cannot be able to run the above software? (first question) I'm not sure what I'm supposed to do, after downloading freebios, but I'm unsure of its function too. In the donwload page of linuxbios.org there is a link to "other software", I have to download that too? I'll be grateful for any hints and I apologize if this is not the right place to ask for it. Bye Uberto Barbini

2 1

Re: Fixes for Tyan s2880
by YhLu 28 Jul '03

28 Jul '03

Ron, It seems that you roll back to the tree, because of Stefan's complain. I want to give detail description on the coherent_ht.c and raminit.c 1. coherent_ht.c add two function: notify_bsp_ap_is_stopped. And wait_ap_stop. 2. raminit.c change csbase counting methods. Any way you at least can put files on s2880 for me. Also please send the Config.lb to me and I would to test the new config tool. Thanks. Regards Yinghai Lu -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年7月24日 21:31 收件人: linuxbios(a)clustermatic.org 主题: Fixes for Tyan s2880 Yh Lu needed to add a mainboard-specific initialization code for the Tyan s2880 board, and needed it called at a special place in hardwaremain(). In V1, we would use defines and other such trickery to get this capability. We're trying to avoid that in V2. This problem turns out to be a perfect use for the static device initialization support. First, we apply patches that are tyan-only or are bug fixes to these files: src/include/device/pci_ids.h src/mainboard/tyan/s2880/auto.c src/mainboard/tyan/s2880/Config src/mainboard/tyan/s2880/debug.c src/mainboard/tyan/s2880/failover.c src/mainboard/tyan/s2880/static_devices.c src/mainboard/tyan/s2880/tyan-fallback.config src/mainboard/tyan/s2880/tyan-normal.config src/mainboard/tyan/s2880/VERSION src/mainboard/tyan/VERSION src/northbridge/amd/amdk8/coherent_ht.c src/northbridge/amd/amdk8/raminit.c src/southbridge/amd/amd8111/Config src/southbridge/amd/amd8111/Config.lb src/southbridge/amd/amd8131/amd8131_bridge.c targets/tyan/s2880/Config.lb Now, we need to ensure that YhLu's "special code" is called for his mainboard. As it happens, the mainboard is also a "chip" in the new scheme. The config tool builds a tree based on this structure, from src/include/device/chip.h: struct chip { struct chip_control *control; /* for this device */ char *path; /* can be 0, in which case the default is taken */ char *configuration; /* can be 0. */ int irq; struct chip *next, *children; /* there is one of these for each INSTANCE of a chip */ void *chip_info; /* the dreaded "void *" */ }; The tree for the s2880 looks like this: ===== #include <device/chip.h> struct chip static_root, static_dev1, static_dev2, static_dev3, static_dev4, sta tic_dev5, static_dev6, static_dev7, static_dev8, static_dev9, static_dev10; #include "/home/rminnich/src/bios/freebios2/src/mainboard/tyan/s2880/chip.h" struct chip static_root = { /* mainboard /home/rminnich/src/bios/freebios2/src/mainboard/tyan/s2880 */ .children = &static_dev9, }; struct chip static_dev9 = { /* cpu /home/rminnich/src/bios/freebios2/src/cpu/k8 */ .next = &static_dev8, }; . . . ====== (the rest is removed for clearness) Note that there are even "chips" for CPUs: it is possible to handle CPU fixup in this system. Each entry in the above structures defines a static device. Please recall that static devices consist of a generic structure and then special-purpose (device specific) structures. The generic structure is this: /* there is one of these for each TYPE of chip */ struct chip_control { void (*enable)(struct chip *, enum chip_pass); char *path; /* the default path. Can be overridden * by commands in config */ // This is the print name for debugging char *name; }; Device-specific classes are defined by the attributes of the device, and hence vary for each device. In the V1 days, we tried to have one generic structure, but that did not even work for the limited case of superio's, so for V2 we are making the structure unique to each device. We have to define one device structure for the Tyan s2880. The structure has to be defined in an include file that is in the directory that contains the code for the device. So, for the tyan s2880 mainboard, we need to have a definition file in src/mainboard/tyan/s2880. We'll call it src/mainboard/tyan/s2880/chip.h. In this case, it is rather simple: struct mainboard_tyan_s2880_config { int fixup_scsi; }; This is the only thing we're controlling at present. Note that the name of the struct is a 'flattened' version of the device name. We need to tell the config tool where to find the file containing the structure, and how to initialize the struct in the file. Add these lines to src/tyan/s2880/Config.lb. They will define the name of the file to use, and the code to initialize the static device. config chip.h register "fixup_scsi" = "1" We need to create the structure that defines the generic structure for the mainboard, so linuxbios can hook into it. So add these lines to the end of src/mainboard/tyan/s2880/mainboard.c: struct chip_control mainboard_tyan_s2880_control = { enable: enable, name: "Tyan s2880 mainboard " }; Then add the enable function (BEFORE the struct chip_control declaration). Note that it is declared 'static', and has only one entry in the switch. static void enable(struct chip *chip, enum chip_pass pass) { struct mainboard_tyan_s2880_config *conf = (struct mainboard_tyan_s2880_config *)chip->chip_info; switch (pass) { default: break; case CONF_PASS_PRE_BOOT: if (conf->fixup_scsi) onboard_scsi_fixup(); printk_debug("mainboard fixup pass %d done\r\n", pass); break; } } That's pretty much it. total changes are 170 lines. The static device tree (which is generated by the config tool, you don't have to write this code) now looks like this: ========== #include <device/chip.h> struct chip static_root, static_dev1, static_dev2, static_dev3, static_dev4, sta tic_dev5, static_dev6, static_dev7, static_dev8, static_dev9, static_dev10; #include "/home/rminnich/src/bios/freebios2/src/mainboard/tyan/s2880/chip.h" extern struct chip_control mainboard_tyan_s2880_control; struct mainboard_tyan_s2880_config mainboard_tyan_s2880_config_0 = { .fixup_scsi = 1, }; struct chip static_root = { /* mainboard /home/rminnich/src/bios/freebios2/src/mainboard/tyan/s2880 */ .children = &static_dev9, .control= &mainboard_tyan_s2880_control, .chip_info = (void *) &mainboard_tyan_s2880_config_0, }; struct chip static_dev9 = { /* cpu /home/rminnich/src/bios/freebios2/src/cpu/k8 */ .next = &static_dev8, }; ===== Note that the mainboard now has several new entries, and there is a new struct for controlling the mainboard, along with an initializer. The enable function for the mainboard will be called at several places in hardwaremain with a different pass #, and since there is only one case defined, only one action is taken. So to add this capability for this mainbard, we had to: - define a file containing the device-specific structure which we called chip.h, and placed in src/mainboard/tyan/s2880 - add two lines to src/mainboard/tyan/s2880/Config.lb, which define the file we need (chip.h) and the initialization of the structure. - add the "base class" structure to src/mainboard/tyan/s2880/mainboard.c, along with the enable function. I've built this mainboard and hexdump of the romimage looks pretty good. Yh Lu, can you please verify this? The config.lb is in targets/tyan/s2880/Config.lb. I can send the context diffs if that will help. Note that this technique will work for anything that the config tool considers a 'device': mainboard, cpu, north and south bridge, superio, etc. Thanks ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

6 10

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