coreboot December 2003

coreboot@coreboot.org

39 participants
66 discussions

legacy BIOS usage
by Ryan Underwood 08 Dec '03

08 Dec '03

Hi, I had the idea of using LinuxBIOS but also maintaining a legacy BIOS for debugging and dual boot scenarios. It would be linked into the LinuxBIOS image and jumped to alternatively depending on the user input. However, thinking about this gave me 2 questions: 1. Are there any forms of user input possible into LinuxBIOS loader? Is the system initialized enough to accept a keyboard input, or ACPI system button, or even something sillier like checking if a PS/2 mouse is plugged in (the user can unplug the mouse to signal LinuxBIOS to jump to the legacy BIOS instead). 2. Is it possible to get the machine into a state where it can check whatever form of user input is possible, but still be able to then put the machine back into a state where the legacy BIOS won't be confused. Or could something like this be done via the reboot vector instead? Power on clean gets you LinuxBIOS, but reboot goes to legacy BIOS... I guess the problem there again would be putting the hardware back into a state that the legacy BIOS can use. any ideas on that topic? It would be nice to use FreeDOS occasionally for testing some external hardware control programs, but FreeDOS requires a PC BIOS, of which there are no open source implementations that I know of. :( Maybe that can be a project for the future, but somehow I see a lack of interest in putting any new effort into a dead platform, so using the legacy proprietary BIOS might be the only real world choice. p.s. there is a broken Microsoft link in the FAQ, it is here now: http://www.microsoft.com/whdc/hwdev/archive/BUSBIOS/pciirq.mspx -- Ryan Underwood, <nemesis(a)icequake.net>

3 3

答复: for all k8 builders
by YhLu 08 Dec '03

08 Dec '03

Eric, I mean in the amdk8_scan_chains, you need to put > config_busses &= 0x000fc88; > config_busses |= > (3 << 0) | /* rw enable, no device compare */ > (( nodeid & 7) << 4) | > (( link & 3 ) << 8) | > ((dev->link[link].secondary) << 16) | > ((dev->link[link].subordinate) << 24); > f1_write_config32(config_reg, config_busses); before /* Now we can scan all of the subordinate busses i.e. the > chain on the hypertranport link */ > max = hypertransport_scan_chain(&dev->link[link], max); YH.

2 1

Re: for all k8 builders
by YhLu 08 Dec '03

08 Dec '03

Eric, Please check the northbridge.c attached. It seems you should modify the e0 before you do the hypertransport_scan_chain. Otherwise you can not access the buses. YH. config_busses &= 0x000fc88; config_busses |= (3 << 0) | /* rw enable, no device compare */ (( nodeid & 7) << 4) | (( link & 3 ) << 8) | ((dev->link[link].secondary) << 16) | ((dev->link[link].subordinate) << 24); f1_write_config32(config_reg, config_busses); #if 1 printk_debug("Hyper transport scan link: %d max: %d\n", link, max); #endif /* Now we can scan all of the subordinate busses i.e. the chain on the hypertranport link */ max = hypertransport_scan_chain(&dev->link[link], max);

2 1

Re: for all k8 builders
by YhLu 08 Dec '03

08 Dec '03

If only - Fix amdk8_scan_root_bus and amdk8_scan_chains so multiple HT chains can be scanned in any order it will not break the code. There must some other file changes cause that. YH. -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年12月8日 12:12 收件人: Eric W. Biederman 抄送: linuxbios(a)clustermatic.org 主题: Re: for all k8 builders On 8 Dec 2003, Eric W. Biederman wrote: > Grumble. You are pushing out my changes before we have finished > testing them. I don't mind to much but I do know some of that code > was not fully generalized, so there could be problems if you have > not looked through it carefully. The problem was that builds that worked friday stopped working this morning, due apparently to this: Revision 1.9 - (download), view (text) (markup) (annotate) - [select for diffs] Sat Dec 6 00:11:56 2003 UTC (2 days, 19 hours ago) by ebiederm CVS Tags: HEAD Changes since 1.8: +21 -8 lines Diff to previous 1.8 - Fix amdk8_scan_root_bus and amdk8_scan_chains so multiple HT chains can be scanned in any order === it was your push, not mine. It broke all the K8 builds. I would normally not have pushed your stuff out but this was kind of an emergency. Trust me, I'm not going to push your changes out before we test 'em, but I can't stop you from doing it :-) thanks ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

3 3

Re: for all k8 builders
by YhLu 08 Dec '03

08 Dec '03

I will check the code.

1 0

for all k8 builders
by ron minnich 08 Dec '03

08 Dec '03

your builds are broken today due to the missing amdk8.h file in src/northbridge/amd/amdk8. Do an update; I just added it. ron

2 3

Hardware Help with diskonchip?
by Devi Priya 07 Dec '03

07 Dec '03

Hi, In the application note (AP044) from Msystems it is given as: "The DiskOnChip Millennium is mapped into an 8KB memory window in the host platforms memory map. This 8KB window consists of four 2KB windows." Why is this mapping done? Is this mapping done in hardware? I use diskonchip millennium (8MByte MD2800). Then shouldn't the entire 8MB shall be mapped in hardware to the physical address space? The steps for BIOS is summarised as 1. After DiskOnChip Millennium BUSY# signal is negated, the CPU fetches the Reset Vector from the Boot-Block area, fetches the Boot Code stored there, and starts to execute the code. 2. Boot Code runs the first part of BIOS, initializing the basic hardware functionality. 3. Boot Codes loads the rest of the BIOS from the flash memory to the DRAM, and transfer control (jumps) there. 4. Chip Select of DiskOnChip Millennium is remapped from Reset Vector to BIOS expansion area. 5. CPU executes the rest of the BIOS code, including ROM expansion devices (among them, the DiskOnChip Millennium itself). 6. CPU calls OS bootstrap loader (INT19). 7. OS is loaded, and recognizes the DiskOnChip Millennium as the boot device. 8. OS loads the application code from the DiskOnChip Millennium and executes it. 9. Application software uses DiskOnChip Millennium exactly as if it were using a regular hard disk. In step 4 why is this remapping done? Is this mapping done in hardware? In my setup, the diskonchip is mapped in hardware to the higher order address (0xFFFFFFFF-0xFF800000). SDRAM mapped to lower address (0x00000000-0x1FFFFFF). What else modification do i require in HARDWARE to use diskonchip millennium? _________________________________________________________________ Add zing to Hotmail. Get FREE newsletters. http://server1.msn.co.in/features/general/Newsletters/index.asp Subscribe now!

1 0

Will this work ??
by Stefan 06 Dec '03

06 Dec '03

Hi there, I've a Gigabyte GA-7NNXP with nForce II Chipset, and a BIOS with a size of 512 KB. Will I be able to get a open source "bios" work on that mainboard ? thx for your helping!!

5 4

Re: Tyan S2885
by YhLu 05 Dec '03

05 Dec '03

S2885 updated to 1.1.5 Only reset once.

1 0

Re: Tyan S2885
by YhLu 05 Dec '03

05 Dec '03

Eric, Great, it works. Even normal scan it can find out 8151. But the bus number is funny, I may need to update bus number mptable.c and irq_table.c and reset.c I wonder if 8151 on CPU 1 and 8131/8111 on CPU0. is the amdk8_scan_root_bus called two times? If so, you may keep the > for(reg = 0xe0; reg <= 0xec; reg += 4) { > value = f1_read_config32(reg); > printk_debug("amdk8_scan_root_bus %0x = %0x max = %0x\n", > reg,value,max); > if((value>>24)>max) > f1_write_config32(reg, 0); > } Regards YH. -----邮件原件----- 发件人: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] 发送时间: 2003年12月5日 15:26 收件人: YhLu 抄送: ron minnich; Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: Tyan S2885 YhLu <YhLu(a)tyan.com> writes: > Eric, > > I change amdk8_scan_root_bus to: > > unsigned int amdk8_scan_root_bus(device_t root, unsigned int max) > { > unsigned reg; > uint32_t value; > /* Unmap all of the other pci busses */ > printk_debug("\nbefore pci_scan_bus\n"); > for(reg = 0xe0; reg <= 0xec; reg += 4) { > value = f1_read_config32(reg); > printk_debug("amdk8_scan_root_bus %0x = %0x max = %0x\n", > reg,value,max); > if((value>>24)>max) > f1_write_config32(reg, 0); > } > for(reg = 0xe0; reg <= 0xec; reg += 4) { > value = f1_read_config32(reg); > printk_debug("amdk8_scan_root_bus %0x = %0x max = %0x\n", > reg,value,max); > } > > max = pci_scan_bus(&root->link[0], PCI_DEVFN(0x18, 0), 0xff, max); > > printk_debug("after pci_scan_bus\n"); > for(reg = 0xe0; reg <= 0xec; reg += 4) { > value = f1_read_config32(reg); > printk_debug("amdk8_scan_root_bus %0x = %0x max = %0x\n", > reg,value,max); > } > > return max; > } > > I think as least you only need to clear the regs that contain bigger bus > number than the next bus for scanning. > > The result will be in the end. > > The problems: > 1. It can not access 8151 on CPU link0 and so can not scan it > 2. The HT scan seems can not figure out and set the link and read/write > enable bit in e0. It set the e0 to 0x05050000 Doh. The Opteron is too forgiving when you only have one link. It makes this kind of debugging a pain. What I am doing should not work but it does in that case... My apologies, for missing this. In amdk8_scan_chains() there is the snippet: config_busses &= 0x0000ffff; config_busses |= ((dev->link[link].secondary) << 16) | ((dev->link[link].subordinate) << 24); f1_write_config32(config_reg, config_busses); Which is the offending piece of code. It neither sets the link that we are supposed to go out, nor does it set the r/w enable bits. Ouch. It only works if those registers are pre programmed. So I think this should be: config_busses &= 0x000fc88; config_busses |= (3 << 0) | /* rw enable, no device compare */ (( nodeid & 7) << 4) | (( link & 3 ) << 8) | ((dev->link[link].secondary) << 16) | ((dev->link[link].subordinate) << 24); f1_write_config32(config_reg, config_busses); Eric

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot December 2003