coreboot

coreboot@coreboot.org

10 participants
39711 discussions

FILO features request
by YhLu 18 Apr '04

18 Apr '04

Eric, Are you adding features to filo? I hope it can 1. understand grub.conf in HD --- and append console=tty0 console=ttyS0,115200 automatically 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and append console=tty0 console=ttyS0,115200 automatically 3. editor to boot command line 4. auto items for elf image in rom ( 64k or 32k segement from 0xfff80000) mem@0xfff80000 mem@0xfff90000 mem@0xfffa0000 mem@0xfffb0000 .... Regards YH

5 6

flash_rom Problem
by Thomas Spear 16 Apr '04

16 Apr '04

This is what happens when I try to build flash_rom: root@(none):/home/freebios2/util/flash_and_burn# make gcc -O2 -g -Wall -Werror -c -o flash_rom.o flash_rom.c gcc -O2 -g -Wall -Werror -c -o flash_enable.o flash_enable.c flash_enable.c:3: pci/pci.h: No such file or directory make: *** [flash_enable.o] Error 1 Someone please tell what I've done wrong. Where does "pci/pci.h" come from? The romimage seems to build ok (I don't really know since I can't flash the rom and try it). Thanks. _________________________________________________________________ >From must-see cities to the best beaches, plan a getaway with the Spring Travel Guide! http://special.msn.com/local/springtravel.armx

4 3

epia-m IRQ routing
by ron minnich 16 Apr '04

16 Apr '04

kernel 2.4.25 can't use the PIRQ table on epia-m. I think the table is right. Anyone know if the 2.4.25 kernel can handle this router on this board? This is the last hold-up: ethernet irq is not working out. 'No IRQ found ...' ron

2 2

答复: 答复: Broadcom NIC, MPTable and APIC ID for HDAMA [PMX:#]
by YhLu 16 Apr '04

16 Apr '04

The arima's PCI-X ioapic is poorly connected. -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月16日 14:42 收件人: YhLu 抄送: Eric Biederman; LinuxBIOS 主题: Re: 答复: Broadcom NIC, MPTable and APIC ID for HDAMA [PMX:#] On Fri, 2004-04-16 at 11:21, YhLu wrote: > That's decided by HW. > Do you mean even the device is behind the PCIX bridge, it's IRQ is not routed by the APIC on the bridge ? Ollie > YH > > -----邮件原件----- > 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] > 发送时间: 2004年4月16日 10:07 > 收件人: Eric Biederman; LinuxBIOS > 主题: Broadcom NIC, MPTable and APIC ID for HDAMA > > Eric, > > The broadcom nic on hdama is connected behind the 8131. > So the IRQ should be routed by the APIC on 8131, right ? > But in the current mptable.c it is > > /* PCI Ints: Type Polarity > Trigger > Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ > /* On board nics */ > smp_write_intsrc(mc, mp_INT, > MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, > bus_8131_1, (0x03<<2)|0, 0x02, 0x13); > smp_write_intsrc(mc, mp_INT, > MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, > bus_8131_1, > (0x04<<2)|0, 0x02, 0x13); > > The IRQ is routed by APIC #2 which is in 8111. Is it correct ? > Why is it still working ? > > Ollie > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

1 0

答复: Broadcom NIC, MPTable and APIC ID for HDAMA
by YhLu 16 Apr '04

16 Apr '04

That's decided by HW. YH -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月16日 10:07 收件人: Eric Biederman; LinuxBIOS 主题: Broadcom NIC, MPTable and APIC ID for HDAMA Eric, The broadcom nic on hdama is connected behind the 8131. So the IRQ should be routed by the APIC on 8131, right ? But in the current mptable.c it is /* PCI Ints: Type Polarity Trigger Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ /* On board nics */ smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x03<<2)|0, 0x02, 0x13); smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x04<<2)|0, 0x02, 0x13); The IRQ is routed by APIC #2 which is in 8111. Is it correct ? Why is it still working ? Ollie _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

答复: 答复: epia-m IRQ routing
by YhLu 16 Apr '04

16 Apr '04

2.4.22 is the most stabe one. -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月16日 13:56 收件人: YhLu 抄送: linuxbios(a)clustermatic.org 主题: Re: 答复: epia-m IRQ routing On Fri, 16 Apr 2004, YhLu wrote: > Why just try 2.4.26? I'm stuck to this version for now. I can't try .26 ron

1 0

答复: epia-m IRQ routing
by YhLu 16 Apr '04

16 Apr '04

Why just try 2.4.26? Only tg3.c has problem in opteron MB. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月16日 12:22 收件人: linuxbios(a)clustermatic.org 主题: epia-m IRQ routing kernel 2.4.25 can't use the PIRQ table on epia-m. I think the table is right. Anyone know if the 2.4.25 kernel can handle this router on this board? This is the last hold-up: ethernet irq is not working out. 'No IRQ found ...' ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

Broadcom NIC, MPTable and APIC ID for HDAMA
by Li-Ta Lo 16 Apr '04

16 Apr '04

Eric, The broadcom nic on hdama is connected behind the 8131. So the IRQ should be routed by the APIC on 8131, right ? But in the current mptable.c it is /* PCI Ints: Type Polarity Trigger Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ /* On board nics */ smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x03<<2)|0, 0x02, 0x13); smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x04<<2)|0, 0x02, 0x13); The IRQ is routed by APIC #2 which is in 8111. Is it correct ? Why is it still working ? Ollie

1 0

epia-m 1/2 baud rate fix
by Dave Ashley 16 Apr '04

16 Apr '04

The post for fixing the 1/2 baud rate problem on epia-m is here: http://www.clustermatic.org/pipermail/linuxbios/2003-December/006207.html The earlier post mentioned probably had the setserial workaround but this is no good, you don't get 115200 baud or other baud rates that don't go into 57,600 exactly (like 38,400). I'm on vacation this past week in Florida so haven't been able to assist any on the epia-m work. One thing I noticed in Dmitri's patch is it seemed to cut out all my code to initialize the VT1211's hardware monitor (used for temperature + voltage monitoring). Other stuff seemed to be hacked and slashed out that I found necessary, but didn't appear to be replaced elsewhere. When I get back to the office hopefully I can do a cvs checkout of latest version and give it a shot and see if it works for me. It sounds like it is working for everyone else right now, which is good news, so congrats all around. So if it's this far along, it would be nice to get the SPD auto detection working. Maybe the path to that is integrate all these V1 changes into V2 and do it in V2. -Dave

5 10

"IP-Config: Failed to open eth0" on epia-m
by Larry Matter 16 Apr '04

16 Apr '04

sorry if this is off-topic for this list: I just started trying linuxbios because I am unhappy with how long it takes the standard bios to boot over pxe (though it does work nicely). I have built linuxbios from cvs from 8-apr and used etherboot 5.0.8 as the payload. This works and etherboot succesfully loads my kernel (2.4.22) from my tftp server. The kernel however, fails to open eth0 and so the nfs mount of my root parition fails, etc. The exact same kernel with (almost) identical command line, booted over pxe works just fine. I diff'd the output of the kernel startup and found a few things that might be significant: linuxBIOS/etherboot: via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker http://www.scyld.com/network/via-rhine.html PCI: No IRQ known for interrupt pin A of device 00:12.0. Please try using pci=biosirq. eth0: VIA VT6102 Rhine-II at 0x1400, 00:40:63:d4:17:70, IRQ 0. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. Via BIOS/PXE: via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker http://www.scyld.com/network/via-rhine.html eth0: VIA VT6102 Rhine-II at 0xec00, 00:40:63:d4:17:70, IRQ 5. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. I say "almost" exact same command line because PXE appends "BOOT_IMA" to it, not sure why. I've googled as much as I know how and have not found anything relevent. If anyone has any ideas I would appreciate it. Thanks, Larry Matter

3 5

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