Today i was able to boot via etherboot 5.4.3 coreboot v2. But only with irqpoll. So i generate with getpir a irq_tables.c. I use the axus/tc320 as sample. So i copied the irq_tables.c to src/mainboard/axus/tc320 but after i can't compile any more.
gcc -Wl,--build-id=none -nostdlib -nostartfiles -static -o coreboot_ram -T /home/ryven/Linuxbios/coreboot-v2/src/config/coreboot_ram.ld coreboot_ram.o coreboot_ram.o: In function `write_tables': (.text+0x26f2): undefined reference to `write_pirq_routing_table' collect2: ld returned 1 exit status make[1]: *** [coreboot_ram] Fehler 1 make[1]: Leaving directory `/home/ryven/Linuxbios/coreboot-v2/targets/axus/tc320/tc320/normal' make: *** [normal/coreboot.rom] Fehler 1
So how is the right way?
Regards Markus
On Sat, Mar 22, 2008 at 09:26:10PM +0100, Markus wrote:
Today i was able to boot via etherboot 5.4.3 coreboot v2. But only with irqpoll. So i generate with getpir a irq_tables.c. I use the axus/tc320 as sample. So i copied the irq_tables.c to src/mainboard/axus/tc320 but after i can't compile any more.
gcc -Wl,--build-id=none -nostdlib -nostartfiles -static -o coreboot_ram -T /home/ryven/Linuxbios/coreboot-v2/src/config/coreboot_ram.ld coreboot_ram.o coreboot_ram.o: In function `write_tables': (.text+0x26f2): undefined reference to `write_pirq_routing_table' collect2: ld returned 1 exit status make[1]: *** [coreboot_ram] Fehler 1 make[1]: Leaving directory `/home/ryven/Linuxbios/coreboot-v2/targets/axus/tc320/tc320/normal' make: *** [normal/coreboot.rom] Fehler 1
The output of getpir didn't compile out of the box (I hope that's fixed now, see http://tracker.coreboot.org/trac/coreboot/ticket/70), but that file is not really meant to be copied as is in the source code anyway (but it can be done). I suggest you just modify the axus/tc320 file to your needs, using the values from the getpir output.
Can you post some more information about your board here, e.g. 'lspci -tvnn' and 'superiotool -dV' for reference? If the board works fine with coreboot we should also add it to the list of supported boards in the wiki, and ideally have a status page for it.
Thanks, Uwe.
Am Tue, 25 Mar 2008 20:46:50 +0100 schrieb Uwe Hermann uwe@hermann-uwe.de:
The output of getpir didn't compile out of the box (I hope that's fixed now, see http://tracker.coreboot.org/trac/coreboot/ticket/70), but that file is not really meant to be copied as is in the source code anyway (but it can be done). I suggest you just modify the axus/tc320 file to your needs, using the values from the getpir output.
Can you post some more information about your board here, e.g. 'lspci -tvnn' and 'superiotool -dV' for reference? If the board works fine with coreboot we should also add it to the list of supported boards in the wiki, and ideally have a status page for it.
If somebody can give my an login to the wiki, i will do this.
it compiles but still need irqpool, so something i have done wrong.
Regard Markus
lspci -tvnn -[00]-+-00.0 1078:0001 +-0e.0 10ec:8139 +-12.0 1078:0100 +-12.1 1078:0101 +-12.2 1078:0102 +-12.3 1078:0103 +-12.4 1078:0104 -13.0 0e11:a0f8
./superiotool -dV superiotool r Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0xffff, rev=0xff Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff No Super I/O found
On Tue, Mar 25, 2008 at 11:09:52PM +0100, Markus wrote:
If somebody can give my an login to the wiki, i will do this.
Great, thanks. Please contact Stefan Reinauer stepan@coresystems.de for wiki accounts.
it compiles but still need irqpool, so something i have done wrong.
See my other mail. Other than the irqpoll does it work and boot fine?
./superiotool -dV superiotool r
Which version of superiotool did you use? It should have printed the version number here.
It doesn't seem to detect the Super I/O on this board, can you look in the case and find out which Super I/O this is?
Uwe.
-
Markus -
Uwe Hermann