coreboot July 2003

coreboot@coreboot.org

67 participants
150 discussions

ldscript.ld contents?
by Devi Priya 25 Jul '03

25 Jul '03

Hello, I compiled the linuxbios for sc1200. The ldscript.ld contents looks like this: INCLUDE ldoptions INCLUDE /root/PT06/Reference/LinuxBios/Freebios/freebios/src/arch/i386/config/ldscript.base INCLUDE /root/PT06/Reference/LinuxBios/Freebios/freebios/src/cpu/i386/entry16.lds INCLUDE /root/PT06/Reference/LinuxBios/Freebios/freebios/src/cpu/i386/entry32.lds INCLUDE /root/PT06/Reference/LinuxBios/Freebios/freebios/src/cpu/i386/reset16.lds It looks completely different from the ldscript.ld found in romimages directory. I hope this ldcript.ld is automatically generated when running the python program. Is the entries correct? Or what i should do to correct it? Thanks in advance for any help. With Regards, Priya. _________________________________________________________________ Nagesh Kukunoor's back! With 3 Deewarein. http://server1.msn.co.in/sp03/3deewarein/index.asp Win tickets here.

2 1

Do I need to make Makefile.conf for myself?
by gimyung han 25 Jul '03

25 Jul '03

Thanks to your help, I could succeed in setup dhcp server and tftp And then, I tried to get over to next step, making elfboot image. At first time, I just typed whole command written in the HOWTO, but I failed with "Error: no Makefile.conf " so I changed the original file, "Makefile.conf.in" to "Makefile.conf", then I typed whole command again. After all, I failed and saw following message: "bash: ./mkelfImage: @PERL@: bad Interpreter: No such file or directory exist" Did I need to make my own Makefile.conf instead of changing Makefile.conf.in? If so, How can I make my own? thanks for your help _________________________________________________________________ MSN Messenger를 통해 온라인상에 있는 친구와 대화를 나누세요. http://messenger.msn.co.kr

5 4

Can you check my result, is it right?
by gimyung han 25 Jul '03

25 Jul '03

it is part of the result of booting linux bios on my epia board but i'm not sure I'm doing right........... it's almost end of it........... Wrote linuxbios table at: 00000500 - 0000068c checksum a514 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 37:init_bytes() - zkernel_start:0xfff00000 zkernel_mask:0x0000ffff Found ELF candiate at offset 0 New segment addr 0x94000 size 0x7328 offset 0x60 filesize 0x37e0 (cleaned up) New segment addr 0x94000 size 0x7328 offset 0x60 filesize 0x37e0 Loading Segment: addr: 0x0000000000094000 memsz: 0x0000000000007328 filesz: 0x00Clearing Segment: addr: 0x00000000000977e0 memsz: 0x0000000000003b48 Jumping to boot code at 0x94000 ROM segment 0xffff length 0xfffe reloc 0x9400 Etherboot 5.0.8 (GPL) Tagged ELF for [VIA 86C100] Boot from (N)etwork or from (L)ocal? clocks_per_tick = 504391 N Probing...[VIA 86C100]Found VIA 6102 ROM address 0x0000 rhine.c v1.0.0 2000-01-07 IO address 1800 Ethernet Address: 00:40:63:CB:C8:11 Analyzing Media type,this will take several seconds........OK Linespeed=100Mbs Halfduplex The PCI BIOS has not enabled this device! Updating PCI command 0003->0007. pci_bus 00 pci_device_fn 90 Searching for server (DHCP)... .................. _________________________________________________________________ 보다 빠르고 보기 편한 뉴스. 오늘의 화제는 MSN 뉴스에서 확인하세요. http://www.msn.co.kr/news/

3 3

Fixes for Tyan s2880
by ron minnich 25 Jul '03

25 Jul '03

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

1 0

NOTE: recent commit from YhLu
by ron minnich 25 Jul '03

25 Jul '03

I have just committed the changes from YhLu which he sent this morning. The following files are changed: CVS: src/include/device/pci_ids.h src/mainboard/tyan/s2880/Config CVS: src/mainboard/tyan/s2880/auto.c CVS: src/mainboard/tyan/s2880/failover.c CVS: src/mainboard/tyan/s2880/tyan-fallback.config CVS: src/mainboard/tyan/s2880/tyan-normal.config CVS: src/northbridge/amd/amdk8/coherent_ht.c CVS: src/northbridge/amd/amdk8/raminit.c CVS: src/southbridge/amd/amd8111/Config CVS: src/southbridge/amd/amd8111/Config.lb CVS: src/southbridge/amd/amd8131/amd8131_bridge.c Note that most of this is s2880-specific, with only a few mods to the amd chip files. The next step is to add options for the new config tool to enable mainboard-specific functions to be called. Please make sure your K8 ports still work. I can send the results of a c-diff on request. ron

1 0

2 quick changes to arima/hdama
by ron minnich 25 Jul '03

25 Jul '03

I've temporarily bumped up debugging output inside that file (the romimage gets too big otherwise) and shrunk the size of the tested memory region until I can get it to run faster. ron

1 0

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

24 Jul '03

Good, I will use your new config tool for s2880. -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年7月24日 16:07 收件人: YhLu 抄送: ebiederman(a)lnxi.com; Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: K8 + 2.4.21 + Tyan S2880 YhLu: I can fix your problem without adding the mainboard init function to hardware main, and also without code like this to the include file: ==== #ifdef FINAL_MAINBOARD_FIXUP void final_mainboard_fixup(void); #else # define final_mainboard_fixup() do {} while(0) #endif /* FINAL_MAINBOARD_FIXUP */ ==== All I need to do is add an enable function for the mainboard into the static device tree, and create a structure for your mainboard in the mainboard/tyan/2880 directory. This is pretty easy, and will let us test out the new static device support. But, if I make this change you are going to have to use the new config tool for your mainboard. There is no going back to the old config tool once I make the change. The new config tool is working pretty well, now, however: Greg and Stefan and I are using it, and Greg and I use it exclusively. There are still some glitches here and there but overall it is quite solid. Is this acceptable to you? Stefan, Greg, and I can help you with any problems you encounter with the new config tool. thanks ron

2 1

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

24 Jul '03

Ron, I find the problem. Can you merge the diff the tree? 1. in raminit.c, when computing csbase, should recount from 0 for every memory controllers. Otherwise the memory on second northbridge will not be init properly and can not be used. 2. add start/stop notify function. ( in coherent_ht.c and auto.c) Otherwise when using image that was compiled in non debug mode for auto.c, the second cpu can not be started. Thanks. Yinghai Lu -----邮件原件----- 发件人: YhLu 发送时间: 2003年7月23日 10:41 收件人: 'ebiederman(a)lnxi.com'; 'ron minnich'; 'Stefan Reinauer' 抄送: 'linuxbios(a)clustermatic.org' 主题: Re: K8 + 2.4.21 + Tyan S2880 Eric or Ron or Stepfan, To make the NIC under mem auto-conf code, I have spent one day on it. Here are my findings: 1. Use the most updated code, in the Etherboot stage it will reboot after firt NIC try aborting. 2. I have try to subsutite mem-conf with hard code version, and found another problem, I can not start AP after conherent_ht or memory initization. Only can start and stop in enable_routing function. 3. I have to move back to old code ( Before Eric moved some definition from romcc_io.h to arch/io.h and cpu/p6/msr.h). At this situation, if I use mem-conf, it still can not find broadcom nic in etherboot stage. But after I substitute mem init with hard code one, It can find the nic. I will study the difference today. But anyway what make I can not start AP after conherent_ht or memory init, so strange ??? Regards Yinghai Lu -----邮件原件----- 发件人: YhLu 发送时间: 2003年7月22日 10:41 收件人: 'ebiederman(a)lnxi.com' 抄送: ron minnich; Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: K8 + 2.4.21 + Tyan S2880 Eric, It can be compiled with you new code. But it meet problems in Etherboot stage. In S2880 has two broadcom NIC port in 8131 bus B, and one amd 8111 built-in nic, and even if I hide it in amd8111 init and Etherboot can find it and try to enable it and can not find the PM cap so aborting, in the old linuxbios code (before yesterday) ( with mem hard code), it will go to tickle on Broadcom nic, but in the new code (yesterday check in) ( mem configurable), it will go to MB restarting.??? How about arima broadcom nic position? Regards Yinghai Lu -----邮件原件----- 发件人: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] 发送时间: 2003年7月21日 18:33 收件人: YhLu 抄送: ron minnich; Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: K8 + 2.4.21 + Tyan S2880 YhLu <YhLu(a)tyan.com> writes: > Eric, > > In the auto.c, if I enable : sdram_initialize(&cpu1), the linuxbios need > another 20k. What happened? Only add one line and the same function has been > called ??? All functions are inline and the set of functions called is large. At least I believe that is the issue. And good luck catching up.... While I am away you get a chance. My latest code has changed sdram_initialize one more time to take a cpu count parameter. And perversely this should help because if a function is called in a loop it will only be inlined once instead of multiple times. Eric

3 4

new config tool, static and dynamic trees
by ron minnich 24 Jul '03

24 Jul '03

Greg has implemented the static tree/dynamic tree code mentioned yesterday, and today it passed its first test with flying colors. Greg needed some ide setup done on the southbridge to make his IDE interface work. To effect the change, he had to have certain code execute at a certain pass in the platform startup. Turned out the code could execute once PCI was configured. His code in the mainboard Config.lb did not change: southbridge winbond/w83c553 end That's it. But the C code for the southbridge had the CONF_PASS_POST_PCI code added for configuration: void southbridge_init(struct chip *chip, enum chip_pass pass) { struct southbridge_winbond_w83c553_config *conf = (struct southbridge_winbond_w83c553_config *)chip->chip_info; switch (pass) { case CONF_PASS_POST_PCI: w83c553_init(); break; default: /* nothing yet */ break; } } The tail end of the code looks like this: struct chip_control southbridge_winbond_w83c553_control = { enable: southbridge_init, name: "Winbond W83C553" }; This last bit is the chip_control structure, the "class definition" code for this part. So, in short, it was trivial to set up, and showed, at least to us, that this is a good direction. ron

3 13

AMD package/part numbers
by Greg Watson 24 Jul '03

24 Jul '03

Any idea how to translate an AMD package number to an AMD part number? I have a flash part that is marked D323GB90V1 but I can't find anything on the AMD site that helps translate this to a part number, short of reading every data sheet. Thanks, Greg

1 0

← Newer
1
2
3
4
5
6
7
...
15
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 July 2003