coreboot September 2008

coreboot@coreboot.org

59 participants
415 discussions

CAR for C7
by bari 05 Sep '08

05 Sep '08

Anyone know the status of a patch for C7 CAR? We have most of the wrinkles ironed out of the C7 + cn700 + vt8237 boards now. Many patches to follow. -Bari

4 10

inline asm peculiarities in v3
by Carl-Daniel Hailfinger 05 Sep '08

05 Sep '08

Hi, I decided to look at all cases of inline asm in our v3 code and I found a few bits which either work by accident or need better documentation. We use __asm__ and asm, __volatile__ and volatile. Can we please decide which one we want, then I'll switch the tree over. northbridge/amd/geodelx/vsmsetup.c:143 > __asm__(".text\n" "real_mode_switch_end:\n"); > extern char real_mode_switch_end[]; AFAICS the compiler and linker are free to place the resulting code anywhere in the binary independent of each other. include/arch/x86/amd/k8/k8.h:746 > static void disable_cache_as_ram_bsp(void) > { > __asm__ volatile ( > // "pushl %eax\n\t" > "pushl %edx\n\t" > "pushl %ecx\n\t" > ); > > disable_cache_as_ram(); > __asm__ volatile ( > "popl %ecx\n\t" > "popl %edx\n\t" > // "popl %eax\n\t" > ); > } The pushl and popl instructions seem to serve no real purpose. Kill them? The K8 CAR disabling has inline asm depending on good compiler behaviour and luck. Patch will be sent separately. Regards, Carl-Daniel -- http://www.hailfinger.org/

3 5

IASL has moved
by ron minnich 05 Sep '08

05 Sep '08

This page: http://www.coreboot.org/FAQ references this page: http://www.intel.com/technology/iapc/acpi/downloads.htm which is gone :-( search for iasl says: Your search - iasl - did not match any documents. No pages were found containing "iasl" oh boy. But there is a package from yum :-) ron

2 4

[PATCH] libpayload: serial output 8 bit clean
by Ulf Jordan 05 Sep '08

05 Sep '08

The attached patch makes the serial output function serial_putchar() 8 bit clean. The motivation for this is that the low level driver should not modify the data in unexpected ways. Furthermore translate_special_chars() is removed, since that functionality is now provided by the ACS machinery in tinycurses. Compile and runtime tested with coreinfo+libpayload+coreboot-v3 under QEMU. /ulf

2 2

r3565 - trunk/payloads/libpayload/drivers
by svn＠coreboot.org 05 Sep '08

05 Sep '08

Author: stuge Date: 2008-09-04 23:05:59 +0200 (Thu, 04 Sep 2008) New Revision: 3565 Modified: trunk/payloads/libpayload/drivers/serial.c Log: Make the serial output driver 8 bit clean. Remove translate_special_chars(), since it has been superseeded by the ACS code in tinycurses. Signed-off-by: Ulf Jordan <jordan(a)chalmers.se> Acked-by: Peter Stuge <peter(a)stuge.se> Modified: trunk/payloads/libpayload/drivers/serial.c =================================================================== --- trunk/payloads/libpayload/drivers/serial.c 2008-09-04 13:44:00 UTC (rev 3564) +++ trunk/payloads/libpayload/drivers/serial.c 2008-09-04 21:05:59 UTC (rev 3565) @@ -37,25 +37,6 @@ #define DIVISOR (115200 / CONFIG_SERIAL_BAUD_RATE) #endif -/* This is a hack - we convert the drawing characters to ASCII */ - -static unsigned char translate_special_chars(unsigned char c) -{ - switch(c) { - case 196: - return '-'; - case 179: - return '|'; - case 218: - case 191: - case 192: - case 217: - return '+'; - default: - return ' '; - } -} - void serial_init(void) { #ifdef CONFIG_SERIAL_SET_SPEED @@ -82,9 +63,6 @@ void serial_putchar(unsigned char c) { - if (c > 127) - c = translate_special_chars(c); - while ((inb(IOBASE + 0x05) & 0x20) == 0) ; outb(c, IOBASE); }

1 0

Re: [coreboot] via vt82c686 southbridge
by a a 04 Sep '08

04 Sep '08

Corey Osgood wrote: > On Thu, Sep 4, 2008 at 11:55 AM, Daniel Lindenaar wrote: >> Hi everybody, >> Too bad, first test boot didn't work... at all... I expected the early >> serial stuff to work at least (as this was already in svn, but...) >> >> I'm using a very simple null-modem cable with only rx,tx and ground wired. >> Is this enough or does coreboot require a more complete cable? >> >> Also, do I need some special settings to enable the debugging output? >> >> I really feel like the newbie now, asking these basic questions :), but I >> also would really like to get this thing working on this motherboard... >> >> regards Daniel > > Nope, that cable should be plenty, as long as it's good. A couple > things to check, when I wrote vt82c686's early serial stuff, I may > have configured it to use the second serial output, because I think > that's all my board had. I can't remember though, so check the > datasheet (I can't right now). Also, check that your debugging setup > actually works, boot linux with the stock bios and "console=tty0 > console=ttyS0,115200" passed to linux. If you don't get a linux boot > log, something's wrong with your serial setup. If everything checks > out, send me a compressed copy of your tree, and I'll try to find the > problem. > > -Corey > > -- > coreboot mailing list > coreboot(a)coreboot.org > http://www.coreboot.org/mailman/listinfo/coreboot > > as far as i know the vt82c686 was already supported by coreboot v2.. i have it more or less working for my netier netexpress xl2000 first thing to check if no serial output is the io address op the superio eg 2E vs 4E ect greetings, todthgie _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

2 1

Added Shuttle SN25P wiki page & links
by Vincent Legoll 04 Sep '08

04 Sep '08

Hello, While I still have that info fresh in my head, I wrote what I did for the Shuttle SN25P mainboard port. main page: http://www.coreboot.org/Shuttle_SN25P linked from entry in supported mainboards Thanks to all who helped me getting there, I hope collaboration will continue. -- Vincent Legoll

4 6

[PATCH] v3: fix initial printk buffer address initialization
by Carl-Daniel Hailfinger 04 Sep '08

04 Sep '08

Fix initial printk buffer address initialization. This was broken in r785 (move from explicit asm to implicit C) and unfortunately qemu never triggered the bug, only real hardware did. Thanks to Ron for bisecting this. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: corebootv3-printk_buffer_addr_init/lib/console.c =================================================================== --- corebootv3-printk_buffer_addr_init/lib/console.c (Revision 856) +++ corebootv3-printk_buffer_addr_init/lib/console.c (Arbeitskopie) @@ -82,7 +82,9 @@ void printk_buffer_init(void) { - struct printk_buffer *buf = printk_buffer_addr(); + struct printk_buffer *buf = (struct printk_buffer *)PRINTK_BUF_ADDR_CAR; + global_vars()->printk_buffer = buf; + buf = printk_buffer_addr(); buf->len = PRINTK_BUF_SIZE_CAR - sizeof(struct printk_buffer); buf->readoffset = 0; buf->writeoffset = 0; -- http://www.hailfinger.org/

2 4

Re: [coreboot] via vt82c686 southbridge
by Daniel Lindenaar 04 Sep '08

04 Sep '08

Hi everybody, Too bad, first test boot didn't work... at all... I expected the early serial stuff to work at least (as this was already in svn, but...) I'm using a very simple null-modem cable with only rx,tx and ground wired. Is this enough or does coreboot require a more complete cable? Also, do I need some special settings to enable the debugging output? I really feel like the newbie now, asking these basic questions :), but I also would really like to get this thing working on this motherboard... regards Daniel Quoting "Daniel Lindenaar" <daniel-coreboot(a)lindenaar.eu>: > Hi everybody, > I'm working on getting coreboot going on my 'thintune'. It's a thin > client PC with a custom motherboard based on the via vt8601 North > and vt82c686b south. I'm using coreboot v2 since v3 was stated to be > unstable (Is this the best choice?). > > I started out by porting some of the code for the 82c686 from the v1 > project and using the code for the vt8235 to structure it in the v2 > way. I've no clue if I've done it right or not, but there doesn't > seem to be very much documentation on that (feel free to point out > if there is...). > > I'm currently trying to get it built, but just found out that SMBus > seems to be needed for the RAM stuff, so I'm porting it over from > the 8235. > > Any tips, tricks and remarks are welcome. I'll give word when it > compiles and I've done a test boot. > > regards, > Daniel Lindenaar > > -- > coreboot mailing list > coreboot(a)coreboot.org > http://www.coreboot.org/mailman/listinfo/coreboot > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

log2c, log2f and fms
by Carl-Daniel Hailfinger 04 Sep '08

04 Sep '08

Hi, unless I'm mistaken, the fms() function is equivalent to log2f(), but the former is in asm while the latter is in C. Generally, I'd like to have a libmath.c with all these mathematical functions. Having a file only for log2 variants is not exactly the most optimal tree organization. How do we treat functions which have an optimized asm version but also exist as C code? - Weak functions? - Macro tricks like #ifdef _HAVE_ARCH_LOG2C ? - Kill the optimized asm completely? Regards, Carl-Daniel -- http://www.hailfinger.org/

2 1

← Newer
1
...
35
36
37
38
39
40
41
42
Older →

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 September 2008