coreboot

coreboot@coreboot.org

12 participants
39779 discussions

答复: 答复: 答复: Which kernel for framebuffering?
by YhLu 06 May '04

06 May '04

Are your changes in CVS server? You need to enable CONFIG_BTEXT_CONSOLE -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年5月6日 14:52 收件人: YhLu 抄送: Hendricks David W.; LinuxBIOS 主题: Re: 答复: 答复: Which kernel for framebuffering? On Thu, 2004-05-06 at 15:59, YhLu wrote: > So the IBM MB does't work again? > Can not get output in CRT or sth? > When I checked with David yesterday, it didn't. There is nothing on the screen even for FILO. I think it is due to different HT topology. Ollie > YH > > -----邮件原件----- > 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] > 发送时间: 2004年5月6日 14:46 > 收件人: YhLu > 抄送: Hendricks David W.; LinuxBIOS > 主题: Re: 答复: Which kernel for framebuffering? > > On Wed, 2004-05-05 at 13:39, YhLu wrote: > > did you do anything with the LDT/Resource for VGA Card ? We have problem > on the IBM/e325 which has different HT topology with hdama. > > Ollie > > > > > Worked nicely :) The keyboard worked at FILO, but did not work after the > > kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I > > > guess that's another matter. I'm just very, very happy to see Linux boot > > into a console I can see on a real monitor :) > > > > On Tue, 4 May 2004, YhLu wrote: > > > > > David, > > > > > > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in > CVS > > > ... > > > > > > Also please refer to the matix to see which kernel you want to use. > > > > > > Please make sure enable ati xl framebuffer only in kernel config. ( > don't > > > enable noinit) > > > > > > Regards > > > > > > YH > > > > >

1 0

答复: 答复: 答复: Which kernel for framebuffering?
by YhLu 06 May '04

06 May '04

Framebuffer mode -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年5月6日 14:54 收件人: YhLu 抄送: Hendricks David W.; LinuxBIOS 主题: Re: 答复: 答复: Which kernel for framebuffering? On Thu, 2004-05-06 at 15:59, YhLu wrote: > So the IBM MB does't work again? > Can not get output in CRT or sth? > BTW, does the BTEXT use the graphics card in legacy mode or in framebuffer mode ? Ollie

1 0

答复: Which kernel for framebuffering?
by YhLu 06 May '04

06 May '04

What is your kernel version? 2.6? Please check if the pc_kbd_init is called, 2.6 for X86-64/i386 need keyboard be reset. It assume BIOS has did that for him. Regards YH -----邮件原件----- 发件人: Hendricks David W. [mailto:dwh@lanl.gov] 发送时间: 2004年5月5日 12:25 收件人: YhLu 抄送: linuxbios(a)clustermatic.org 主题: Re: Which kernel for framebuffering? Worked nicely :) The keyboard worked at FILO, but did not work after the kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I guess that's another matter. I'm just very, very happy to see Linux boot into a console I can see on a real monitor :) On Tue, 4 May 2004, YhLu wrote: > David, > > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in CVS > ... > > Also please refer to the matix to see which kernel you want to use. > > Please make sure enable ati xl framebuffer only in kernel config. ( don't > enable noinit) > > Regards > > YH > > -----ÓÊ¼þÔ¼þ----- > ·¢¼þÈË: Hendricks David W. [mailto:dwh@lanl.gov] > ·¢ËÍÊ±¼ä: 2004Äê5ÔÂ4ÈÕ 13:31 > ÊÕ¼þÈË: YhLu > ³ËÍ: linuxbios(a)clustermatic.org > Ö÷Ìâ: Which kernel for framebuffering? > > We were able to build and boot LinuxBIOS with VGA support for an HDAMA. > FILO came up on screen and the keyboard worked, but we've been unable to > get Linux framebuffering to work using a 64-bit kernel. We were wondering > if there's anything special you had to do to make it work, or any special > kernel version or patches we need to use. > >

3 2

Pleased experienced on EPIA : Linuxbios runs,but smbus errors, no normal rom starting, payload making difficulties
by Mathieu Deschamps 06 May '04

06 May '04

hello to every linuxBios people, First, I would like I got V2 started on EPIA C3 Ezra with a null payload for a start ...and that truely welcome and pleasant. I heared a while ago of a half baud rate problem, I have no worries on this side. I was trying to to collect debug serial sent strings via minicom, but i would't advice this, it's a mess to configure (in fact for someone like I). I've just make it with this script that I have joined in there if it is of any use to somebody : #!/bin/bash # Hear ! # # ( [ "x$1" = "x" ] && echo "Usage $0 log_file" && exit 0)|| $LOG="$1" ter=`tty` echo "****************************************************" >>$LOG echo " Hear! Boot Log started on `date +%d/%m/%y\|%T` " >> $LOG echo " tty in use : $ter from ttyS0 " >>$LOG echo "****************************************************" >>$LOG cat -sbA </dev/ttyS0 | tee -a $LOG It can be lauch that way : [root@ge] sh hear.sh boot.log [root@ge] cat boot.log | while read line; do if [ "x$line" != "x$" ]; then echo $line;fi;done it outputs the bellow log with some non-fatal (?) error on which, firstly I would like some explanation if you will **************************************************** Hear! Boot Log started on 04/05/04|17:27:54 tty in use : /dev/pts/0 from ttyS0 **************************************************** 1 jM-^^xM-C$ 2 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 starting...$ Why the normal rom didn't start first, though I config 2 payloads normal and fallback. I belived fallback were called in case of fallback BTW of erroring normal rom ?! 3 vt8601 init starting$ 4 Slot 00 is SDRAM 04000000 bytes $ 5 Slot 01 is SDRAM 04000000 bytes $ 6 Slot 02smbus_error: 04$ 7 Device Error$ 8 is empty$ 9 Slot 03smbus_error: 04$ 10 Device Error$ 11 is empty$ What are these error number refers to ? It work though, but these errors while init plus the fallback mode right from the start, show nothing good for the future deployement I presume ... anyway 12 vt8601 done$ 13 POST: 0x39$ 14 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 booting...$ 15 POST: 0x40$ 16 Finding PCI configuration type.$ 17 POST: 0x5f$ 18 Enumerating static devices...$ 19 Enumerating buses...$ 20 POST: 0x24$ 21 POST: 0x25$ 22 POST: 0x24$ 23 POST: 0x25$ 24 POST: 0x55$ 25 POST: 0x55$ 26 done$ 27 POST: 0x66$ 28 Allocating resources...done.$ 29 POST: 0x88$ 30 Enabling resourcess...$ 31 done.$ 32 Initializing devices...$ 33 Devices initialized$ 34 POST: 0x89$ 35 vt8231_init: enabling compatibility IDE addresses$ 36 Ethernet fixup$ 37 pci_routing_fixup: dev is 00017fc0$ 38 setting southbridge$ 39 setting ethernet$ 40 setting pci slot$ 41 pci_routing_fixup: DONE$ 42 POST: 0x70$ 43 totalram: 128M$ 44 Initializing CPU #0$ 45 POST: 0x60$ 46 Enabling cache...POST: 0x6a$ 47 done.$ 48 POST: 0x92$ 49 POST: 0x93$ 50 Disabling local apic...done.$ 51 POST: 0x9b$ 52 CPU #0 Initialized$ 53 POST: 0x75$ 54 POST: 0x9a$ 55 Checking IRQ routing tables...$ 56 done.$ 57 Copying IRQ routing tables to 0xf0000...done.$ 58 Verifing copy of IRQ routing tables at 0xf0000...done$ 59 POST: 0x96$ 60 Welcome to elfboot, the open sourced starter.$ 61 January 2002, Eric Biederman.$ 62 Version 1.3$ 63 POST: 0xf8$ 64 Cannot Load ELF Image$ 65 POST: 0xff$ So this is ok I have not linked any payload, but why does it redo it once more : 66 jM-^^xM-C$ 67 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 starting...$ 68 vt8601 init starting$ 69 Slot 00 is SDRAM 04000000 bytes $ 70 Slot 01 is SDRAM 04000000 bytes $ 71 Slot 02smbus_error: 04$ 72 Device Error$ 73 is empty$ 74 Slot 03smbus_error: 04$ 75 Device Error$ 76 is empty$ 77 vt8601 done$ 78 POST: 0x39$ 79 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 booting...$ 80 POST: 0x40$ 81 Finding PCI configuration type.$ 82 POST: 0x5f$ 83 Enumerating static devices...$ 84 Enumerating buses...$ 85 POST: 0x24$ 86 POST: 0x25$ 87 POST: 0x24$ 88 POST: 0x25$ 89 POST: 0x55$ 90 POST: 0x55$ 91 done$ 92 POST: 0x66$ 93 Allocating resources...done.$ 94 POST: 0x88$ 95 Enabling resourcess...$ 96 done.$ 97 Initializing devices...$ 98 Devices initialized$ 99 POST: 0x89$ 100 vt8231_init: enabling compatibility IDE addresses$ 101 Ethernet fixup$ 102 pci_routing_fixup: dev is 00017fc0$ 103 setting southbridge$ 104 setting ethernet$ 105 setting pci slot$ 106 pci_routing_fixup: DONE$ 107 POST: 0x70$ 108 totalram: 128M$ 109 Initializing CPU #0$ 110 POST: 0x60$ 111 Enabling cache...POST: 0x6a$ 112 done.$ 113 POST: 0x92$ 114 POST: 0x93$ 115 Disabling local apic...done.$ 116 POST: 0x9b$ 117 CPU #0 Initialized$ 118 POST: 0x75$ 119 POST: 0x9a$ 120 Checking IRQ routing tables...$ 121 done.$ 122 Copying IRQ routing tables to 0xf0000...done.$ 123 Verifing copy of IRQ routing tables at 0xf0000...done$ 124 POST: 0x96$ 125 Welcome to elfboot, the open sourced starter.$ 126 January 2002, Eric Biederman.$ 127 Version 1.3$ 128 POST: 0xf8$ 129 Cannot Load ELF Image$ 130 POST: 0xff$ Secondly, I intended to make a IDE elfImagepayload to boot a kernel on a hard disk, I've read that LinuxBios alone could do that quite well. So got mkelfImage 1.16 (i know it's quite old but i can't find a link to a recent one- BTW please a link to a more recent one would be appreciated). I had a error on the build that's seems not to be relevant since ending ok ( that's i like to say to myself in these cases ) [root@ge] make;echo "Build : $?"; find :./kunzip_src: No such file ... Build : 0 So I made : mkelfImage -kernel=/boot/vmlinuz vmlinuz is a kenel bzImage. It made elfImage, that is wierd : ls says : -rwxr-xr-x 1 root root 901816 mai 5 10:08 elfImage file says: elfImage: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linkedfile: corrupted section header size. It's corrupted, could it be the build "warn"-error message ? I've done a readelf -x on it too : En-tête ELF: Magique: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Classe: ELF32 Données: complément à 2, système à octets de poids faible d'abord (little endian) Version: 1 (current) OS/ABI: UNIX - System V Version ABI: 0 Type: EXEC (fichier exécutable) Machine: Intel 80386 Version: 0x1 Adresse du point d'entrée: 0x101c0 Début des en-têtes de programme: 52 (octets dans le fichier) Début des en-têtes de section: 0 (octets dans le fichier) Fanions: 0x0 Taille de cet en-tête: 52 (bytes) Taille de l'en-tête du programme: 32 (bytes) Nombre d'en-tête du programme: 5 Taille des en-têtes de section: 0 (bytes) Nombre d'en-têtes de section: 0 Table d'indexes des chaînes d'en-tête de section: 0 Il n'y a pas de section dans ce fichier. En-têtes de programme: Type Décalage Adr. vir. Adr.phys. T.Fich. T.Mém. Fan Alignement NOTE 0x0000d4 0x00010000 0x00010000 0x001c0 0x001c0 RWE 0 LOAD 0x0000d4 0x00010000 0x00010000 0x0562c 0x058b8 RWE 0 LOAD 0x0058b8 0x00091000 0x00091000 0x00000 0x00028 RWE 0 LOAD 0x0058b8 0x00100000 0x00100000 0xd6a00 0x700000 RWE 0 LOAD 0x0dc2b8 0x00800000 0x00800000 0x00000 0x00000 RWE 0 Il n'y a pas de segement dynamique dans ce fichier. Il n'y a pas de relocalisation dans ce fichier. Il n'y a pas de section unwind dans ce fichier. Aucune information de version repérée dans ce fichier.

1 0

AMD8111 PCI bridge
by YhLu 05 May '04

05 May '04

Eric, If the discard timer is enabled, when using Silicon Image 3114 serial SATA, I can not fisk the disk and format it. Disable it, all operations will be OK. // dword |= (1<<27); /* Discard timer */ dword &= ~(1<<27); /* Discard timer */ Why did you enable it? Regards YH

1 0

答复: 答复: Which kernel for framebuffering?
by YhLu 05 May '04

05 May '04

Please check your pnp_device.c Are there following lines if(info[i].ops == 0) { // BY LYH dev->ops = ops; } else { dev->ops = info[i].ops; // BY LYH } Otherwise you need do one cvs update for that file. YH -----邮件原件----- 发件人: Hendricks David W. [mailto:dwh@lanl.gov] 发送时间: 2004年5月5日 17:26 收件人: YhLu 抄送: linuxbios(a)clustermatic.org 主题: Re: ´ð¸´: Which kernel for framebuffering? I am using kernel 2.6.5. I'm not sure that the pc_kbd_init function exists in kernel 2.6.5. But it does not look like atkbd_init() is called, in case that's what you meant to say. I'll check it out again tomorrow if I have some time. When we cat /proc/interrupts, int 1 does not appear on the list: k root # cat /proc/interrupts CPU0 CPU1 0: 17164403 0 IO-APIC-edge timer 2: 0 0 XT-PIC cascade 4: 8 0 IO-APIC-edge serial 8: 0 0 IO-APIC-edge rtc 12: 41628 0 IO-APIC-edge i8042 14: 23228 0 IO-APIC-edge ide0 15: 2 0 IO-APIC-edge ide1 19: 270954 0 IO-APIC-level eth0 NMI: 181 22 LOC: 17161863 17161969 ERR: 0 MIS: 0 However, this is in our dmesg: k root # dmesg | grep -ie 'kbd' serio: i8042 KBD port at 0x60,0x64 irq 1 Also, the mouse works in X windows. On Wed, 5 May 2004, YhLu wrote: > What is your kernel version? 2.6? > > Please check if the pc_kbd_init is called, 2.6 for X86-64/i386 need keyboard > be reset. It assume BIOS has did that for him. > > Regards > > YH > > -----é‚®ä»¶åŽŸä»¶----- > å‘ä»¶äºº: Hendricks David W. [mailto:dwh@lanl.gov] > å‘é€æ—¶é—´: 2004å¹´5æœˆ5æ—¥ 12:25 > æ”¶ä»¶äºº: YhLu > æŠ„é€: linuxbios(a)clustermatic.org > ä¸»é¢˜: Re: Which kernel for framebuffering? > > Worked nicely :) The keyboard worked at FILO, but did not work after the > kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I > guess that's another matter. I'm just very, very happy to see Linux boot > into a console I can see on a real monitor :) > > On Tue, 4 May 2004, YhLu wrote: > > > David, > > > > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in CVS > > ... > > > > Also please refer to the matix to see which kernel you want to use. > > > > Please make sure enable ati xl framebuffer only in kernel config. ( don't > > enable noinit) > > > > Regards > > > > YH > > > > -----Ã“ÃŠÂ¼Ã¾Ã”ÂÂ¼Ã¾----- > > Â·Â¢Â¼Ã¾ÃˆÃ‹: Hendricks David W. [mailto:dwh@lanl.gov] > > Â·Â¢Ã‹ÃÃŠÂ±Â¼Ã¤: 2004Ã„Ãª5Ã”Ã‚4ÃˆÃ• 13:31 > > ÃŠÃ•Â¼Ã¾ÃˆÃ‹: YhLu > > Â³ÂÃ‹Ã: linuxbios(a)clustermatic.org > > Ã–Ã·ÃŒÃ¢: Which kernel for framebuffering? > > > > We were able to build and boot LinuxBIOS with VGA support for an HDAMA. > > FILO came up on screen and the keyboard worked, but we've been unable to > > get Linux framebuffering to work using a 64-bit kernel. We were wondering > > if there's anything special you had to do to make it work, or any special > > kernel version or patches we need to use. > > > > >

1 0

答复: 答复: Which kernel for framebuffering?
by YhLu 05 May '04

05 May '04

Mine's in s2885 ~ # cat /proc/interrupts CPU0 CPU1 0: 2419417 0 IO-APIC-edge timer 1: 9 0 IO-APIC-edge i8042 2: 0 0 XT-PIC cascade 4: 277 0 IO-APIC-edge serial 8: 0 0 IO-APIC-edge rtc 14: 12 0 IO-APIC-edge ide0 15: 29 0 IO-APIC-edge ide1 17: 2 0 IO-APIC-level libata 19: 3 0 IO-APIC-level ohci1394 NMI: 28 2 LOC: 2418600 2418591 ERR: 0 MIS: 0 ~ # Also in boot message: serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 input: AT Translated Set 2 keyboard on isa0060/serio0 -----邮件原件----- 发件人: Hendricks David W. [mailto:dwh@lanl.gov] 发送时间: 2004年5月5日 17:26 收件人: YhLu 抄送: linuxbios(a)clustermatic.org 主题: Re: ´ð¸´: Which kernel for framebuffering? I am using kernel 2.6.5. I'm not sure that the pc_kbd_init function exists in kernel 2.6.5. But it does not look like atkbd_init() is called, in case that's what you meant to say. I'll check it out again tomorrow if I have some time. When we cat /proc/interrupts, int 1 does not appear on the list: k root # cat /proc/interrupts CPU0 CPU1 0: 17164403 0 IO-APIC-edge timer 2: 0 0 XT-PIC cascade 4: 8 0 IO-APIC-edge serial 8: 0 0 IO-APIC-edge rtc 12: 41628 0 IO-APIC-edge i8042 14: 23228 0 IO-APIC-edge ide0 15: 2 0 IO-APIC-edge ide1 19: 270954 0 IO-APIC-level eth0 NMI: 181 22 LOC: 17161863 17161969 ERR: 0 MIS: 0 However, this is in our dmesg: k root # dmesg | grep -ie 'kbd' serio: i8042 KBD port at 0x60,0x64 irq 1 Also, the mouse works in X windows. On Wed, 5 May 2004, YhLu wrote: > What is your kernel version? 2.6? > > Please check if the pc_kbd_init is called, 2.6 for X86-64/i386 need keyboard > be reset. It assume BIOS has did that for him. > > Regards > > YH > > -----é‚®ä»¶åŽŸä»¶----- > å‘ä»¶äºº: Hendricks David W. [mailto:dwh@lanl.gov] > å‘é€æ—¶é—´: 2004å¹´5æœˆ5æ—¥ 12:25 > æ”¶ä»¶äºº: YhLu > æŠ„é€: linuxbios(a)clustermatic.org > ä¸»é¢˜: Re: Which kernel for framebuffering? > > Worked nicely :) The keyboard worked at FILO, but did not work after the > kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I > guess that's another matter. I'm just very, very happy to see Linux boot > into a console I can see on a real monitor :) > > On Tue, 4 May 2004, YhLu wrote: > > > David, > > > > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in CVS > > ... > > > > Also please refer to the matix to see which kernel you want to use. > > > > Please make sure enable ati xl framebuffer only in kernel config. ( don't > > enable noinit) > > > > Regards > > > > YH > > > > -----Ã“ÃŠÂ¼Ã¾Ã”ÂÂ¼Ã¾----- > > Â·Â¢Â¼Ã¾ÃˆÃ‹: Hendricks David W. [mailto:dwh@lanl.gov] > > Â·Â¢Ã‹ÃÃŠÂ±Â¼Ã¤: 2004Ã„Ãª5Ã”Ã‚4ÃˆÃ• 13:31 > > ÃŠÃ•Â¼Ã¾ÃˆÃ‹: YhLu > > Â³ÂÃ‹Ã: linuxbios(a)clustermatic.org > > Ã–Ã·ÃŒÃ¢: Which kernel for framebuffering? > > > > We were able to build and boot LinuxBIOS with VGA support for an HDAMA. > > FILO came up on screen and the keyboard worked, but we've been unable to > > get Linux framebuffering to work using a 64-bit kernel. We were wondering > > if there's anything special you had to do to make it work, or any special > > kernel version or patches we need to use. > > > > >

1 0

Re: LinuxBIOS Video?
by aphthong＠sizzard.com 05 May '04

05 May '04

So has anyone gotten an ATI video card to work without the emulation BIOS? Jordan At 02:45 PM 4/29/2004, ron minnich wrote: >On Thu, 29 Apr 2004, Li-Ta Lo wrote: > > > Last time I check, the ATI vgabios wanted to install int 0x10 handler > > and call into itself via int 0x10. The emulator can't do this yet. > >Right, I had forgotten this problem. > >Silly VGA BIOS. > >ron > >_______________________________________________ >Linuxbios mailing list >Linuxbios(a)clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios

6 21

答复: 答复: 答复: Disable USB2 in AMD8111 and remove ide hardcode io addr
by YhLu 05 May '04

05 May '04

If I changed config.lb PCI 1:0.2 on --> PCI 1:0.2 off The PCI 1:0.0 and PCI 1:0.1 will be disabled together. According to AMD 8111 data sheet, LPC 0x48, only can be disabled the device in second bus by device num, and the three USB share one device number. So I guess the code about 0x47 must be there. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年5月5日 9:28 收件人: YhLu 抄送: Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: 答复: 答复: Disable USB2 in AMD8111 and remove ide hardcode io addr On Wed, 5 May 2004, YhLu wrote: > I change my mind, disable that in Config.lb is better and less code. good! ron

4 5

答复: Disable USB2 in AMD8111 and remove ide hardcode io addr
by YhLu 05 May '04

05 May '04

According to AMD, USB 2 in amd8111 will never work. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年5月5日 7:07 收件人: YhLu 抄送: Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: Disable USB2 in AMD8111 and remove ide hardcode io addr On Wed, 5 May 2004, ron minnich wrote: > On Tue, 4 May 2004, YhLu wrote: > > > I'm going to add several lines in amd8111_enable of amd8111.c to disable > > USB2 in amd8111. > > > > /* disable usb2 in amd 8111 because it does not work awlays*/ > > byte = pci_read_config8(lpc_dev, 0x47); > > byte |= (1<<7); > > pci_write_config8(lpc_dev, 0x47, byte); > > this is the wrong way to do this, please don't do it just yet. ok, the other two changes look fine. This disabling is fine if the kernel can later re-enable, but I doubt the kernel will do that. We need a way to make this usb enable/disable visible at configuration time, so people can turn on/off as needed, unless usb2.0 on the 8111 NEVER work. I am willing to guess it will work someday, and this built-in disable will come back to bite us. ron

3 2

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