coreboot January 2007

coreboot@coreboot.org

54 participants
112 discussions

[LinuxBIOS] r2536 - trunk/LinuxBIOSv2/util/probe_superio
by svn＠openbios.org 17 Jan '07

17 Jan '07

Author: stepan Date: 2007-01-17 11:57:42 +0100 (Wed, 17 Jan 2007) New Revision: 2536 Modified: trunk/LinuxBIOSv2/util/probe_superio/Makefile trunk/LinuxBIOSv2/util/probe_superio/probe_superio.c Log: trivial enhancement * add fintek superio support * add license header * add clean target in makefile Signed-off-by: Stefan Reinauer <stepan(a)coresystems.de> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/LinuxBIOSv2/util/probe_superio/Makefile =================================================================== --- trunk/LinuxBIOSv2/util/probe_superio/Makefile 2007-01-16 11:56:35 UTC (rev 2535) +++ trunk/LinuxBIOSv2/util/probe_superio/Makefile 2007-01-17 10:57:42 UTC (rev 2536) @@ -1,2 +1,6 @@ +CC:=gcc +CFLAGS:=-O2 -Wall probe_superio: probe_superio.c - cc -O2 -o probe_superio probe_superio.c + $(CC) $(CFLAGS) -o $@ $< +clean: + rm probe_superio Modified: trunk/LinuxBIOSv2/util/probe_superio/probe_superio.c =================================================================== --- trunk/LinuxBIOSv2/util/probe_superio/probe_superio.c 2007-01-16 11:56:35 UTC (rev 2535) +++ trunk/LinuxBIOSv2/util/probe_superio/probe_superio.c 2007-01-17 10:57:42 UTC (rev 2536) @@ -1,7 +1,29 @@ +/* + * This file is part of the LinuxBIOS project. + * + * Copyright (C) 2006 Ronald Minnich <rminnich(a)gmail.com> + * Copyright (C) 2006 coresystems GmbH <info(a)coresystems.de> + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License as published by + * the Free Software Foundation; either version 2 of the License, or + * (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + */ + #include <stdio.h> +#include <stdlib.h> #include <sys/io.h> -/* well, they really thought this throught, eh? Family is 8 bits!!!! */ +/* well, they really thought this through, eh? Family is 8 bits!!!! */ char *familyid[] = { [0xf1] = "pc8374 (winbond, was NS)" }; @@ -41,21 +63,97 @@ } void -probe_idregs(unsigned short port){ +dump_fintek(unsigned short port, unsigned int did) +{ + switch(did) { + case 0x0604: + printf ("Fintek F71805\n"); + break; + case 0x4103: + printf ("Fintek F71872\n"); + break; + default: + printf ("Unknown Fintek SuperIO: did=0x%04x\n",did); + return; + } + + printf("Flash write is %s.\n", regval(port, 0x28)&0x80 ? "enabled" : "disabled"); + printf("Flash control is 0x%04x.\n", regval(port, 0x28)); + printf("27=%02x\n", regval(port, 0x27)); + printf("29=%02x\n", regval(port, 0x29)); + printf("2a=%02x\n", regval(port, 0x2a)); + printf("2b=%02x\n", regval(port, 0x2b)); + + /* select UART 1 */ + outb(0x07, port); + outb(0x01, port+1); + printf("UART1 is %s\n", regval(port, 0x30) & 1 ? "enabled" : "disabled"); + printf("UART1 base=%02x%02x, irq=%02x, mode=%s\n", + regval(port, 0x60), regval(port, 0x61), regval(port, 0x70)&0x0f, + regval(port, 0xf0)&0x10 ? "RS485":"RS232"); + + /* select UART 2 */ + outb(0x07, port); + outb(0x02, port+1); + printf("UART2 is %s\n", regval(port, 0x30) & 1 ? "enabled" : "disabled"); + printf("UART2 base=%02x%02x, irq=%02x, mode=%s\n", + regval(port, 0x60), regval(port, 0x61), regval(port, 0x70)&0x0f, + regval(port, 0xf0)&0x10 ? "RS485":"RS232"); + + /* select Parport */ + outb(0x07, port); + outb(0x03, port+1); + printf("PARPORT is %s\n", regval(port, 0x30) & 1 ? "enabled" : "disabled"); + printf("PARPORT base=%02x%02x, irq=%02x\n", + regval(port, 0x60), regval(port, 0x61), regval(port, 0x70)&0x0f); + + /* select hw monitor */ + outb(0x07, port); + outb(0x04, port+1); + printf("HW monitor is %s\n", regval(port, 0x30) & 1 ? "enabled" : "disabled"); + printf("HW monitor base=%02x%02x, irq=%02x\n", + regval(port, 0x60), regval(port, 0x61), regval(port, 0x70)&0x0f); + + /* select gpio */ + outb(0x07, port); + outb(0x06, port+1); + printf("GPIO is %s\n", regval(port, 0x30) & 1 ? "enabled" : "disabled"); + printf("GPIO 70=%02x, e0=%02x, e1=%02x, e2=%02x, e3=%02x, e4=%02x, e5=%02x\n", + regval(port, 0x70), regval(port, 0xe0), regval(port, 0xe1), regval(port, 0xe2), + regval(port, 0xe3), regval(port, 0xe4), regval(port, 0xe5)); + printf("GPIO e6=%02x, e7=%02x, e8=%02x, e9=%02x, f0=%02x, f1=%02x, f3=%02x, f4=%02x\n", + regval(port, 0xe6), regval(port, 0xe7), regval(port, 0xe8), regval(port, 0xe9), + regval(port, 0xf0), regval(port, 0xf1), regval(port, 0xf3), regval(port, 0xf4)); + printf("GPIO f5=%02x, f6=%02x, f7=%02x, f8=%02x\n", + regval(port, 0xf5), regval(port, 0xf6), regval(port, 0xf7), regval(port, 0xf8)); + + +} + + +void +probe_idregs_simple(unsigned short port){ unsigned char id; - int i; outb(0x20, port); if (inb(port) != 0x20) { - printf("probing 0x%04x, failed (0x%02x), data returns 0x%02x\n", + if (inb(port) == 0xff ) + printf ("No SuperIO chip found at 0x%04x\n", port); + else + printf("probing 0x%04x, failed (0x%02x), data returns 0x%02x\n", port, inb(port), inb(port+1)); return; } id = inb(port+1); - printf("Probe of id returns %02x\n", id); + + printf("SuperIO found at 0x%02x: id = 0x%02x\n", port, id); if (id == 0xff) return; - printf("%s\n", familyid[id]); + if (familyid[id]) + printf("%s\n", familyid[id]); + else + printf("<unknown>\n"); + switch(id) { case 0xf1: dump_ns8374(port); @@ -66,15 +164,63 @@ } } + void +probe_idregs_fintek(unsigned short port){ + unsigned int vid, did; + + // Enable configuration sequence (Fintek uses this for example) + outb(0x87, port); + outb(0x87, port); + + // + outb(0x20, port); + if (inb(port) != 0x20) { + if (inb(port) == 0xff ) + printf ("No SuperIO chip found at 0x%04x\n", port); + else + printf("probing 0x%04x, failed (0x%02x), data returns 0x%02x\n", + port, inb(port), inb(port+1)); + return; + } + did = inb(port+1); + + outb(0x21, port); + did = did|(inb(port+1)<<8); + + outb(0x23, port); + vid = inb(port+1); + outb(0x24, port); + vid = vid|(inb(port+1)<<8); + + printf("SuperIO found at 0x%02x: vid=0x%04x/did=0x%04x\n", port, vid, did); + + if (vid == 0xff || vid == 0xffff) + return; + + // printf("%s\n", familyid[id]); + switch(vid) { + case 0x3419: + dump_fintek(port, did); + break; + default: + printf("no dump for 0x%04x/0x%04x\n", vid, did); + break; + } + + // disable configuration + outb(0xaa, port); +} + +void probe_superio(unsigned short port) { - probe_idregs(port); + probe_idregs_simple(port); + probe_idregs_fintek(port); } int -main(int argc, char *argv[]){ - unsigned short port; - +main(int argc, char *argv[]) +{ if (iopl(3) < 0) { perror("iopl"); exit(1); @@ -84,4 +230,6 @@ probe_superio(0x2e); /* now try the 4e */ probe_superio(0x4e); + + return 0; }

1 0

[LinuxBIOS] epia, rom_cc and locking code
by Ben Hewson 16 Jan '07

16 Jan '07

Ok first off the issue with ROM_CC and #if - #else - #endif not compiling properly. After some testing I have at least found the problem and it only ever happens if you put a C++ style comment on the same line as the #if or #else so in the following example static void test_ifdef(void) { #if TEST_IFDEF // blows up outb(50,100); outb(51,100); outb(52,100); #else /* ok */ outb(60,100); outb(61,100); outb(62,100); #endif } Of course no comment works fine as well. Also putting a blank line after the comment produces the correct code. I can't say for the rest of the linuxbios code, but the via/epia code seems to have a good mixture of both types of comments. Perhaps as the code is not strictly C++ you should stick to using standard C style comments. Ok now to my problems with the EPIA board. I think in general it is working ok, but I still have some problems. >From a cold boot and also at other times, it will just hang. I am having problems tracking down just where it hangs. At first sight it appears to happen inside the SMBus read function, but that is a guess from the debug output. The problem I get is if I try and add any debug output inside SMBus read it gets worse and locks more frequently. If I have the memory test enabled it can also lock up when doing the verify. So I guess I can think of 3 reason for it to lock. 1. Some enabled, but not handled interrupt is happening. (I would assume that all interrupts are disabled at powerup but hardware so this is probably not it) 2. Southbridge is not configured properly. (would be very bad chip design if the SMBus part of the southbridge interferred with the rest of the functionality) 3. It is actually running, but serial output has stopped. ( don't think this is the case as it never boots up) I guess I need to look for loops that can become locked, probably withing the serial output code. Can anyone think of some other reason for it to lock up ?

3 6

[LinuxBIOS] #60: Change 'ram' to 'RAM' in user-visible output
by LinuxBIOS 16 Jan '07

16 Jan '07

#60: Change 'ram' to 'RAM' in user-visible output ----------------------------------+----------------------------------------- Reporter: uwe | Owner: uwe Type: enhancement | Status: new Priority: minor | Milestone: Cosmetic fixes Component: code | Version: v2 Keywords: | Dependencies: Patchstatus: patch needs review | ----------------------------------+----------------------------------------- Change 'ram' to 'RAM' in user-visible output. Signed-off-by: Uwe Hermann <uwe at hermann-uwe.de> --- Patch is available at http://www.openbios.org/pipermail/linuxbios/2006-December/017610.html or directly at http://www.openbios.org/pipermail/linuxbios/attachments/20061210/c82afdec/a… -- Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/60> LinuxBIOS <http://www.linuxbios.org/>

1 2

[LinuxBIOS] r2535 - in trunk/LinuxBIOSv2/src: arch/i386/init cpu/amd/car cpu/x86/car
by svn＠openbios.org 16 Jan '07

16 Jan '07

Author: uwe Date: 2007-01-16 12:56:35 +0100 (Tue, 16 Jan 2007) New Revision: 2535 Modified: trunk/LinuxBIOSv2/src/arch/i386/init/crt0.S.lb trunk/LinuxBIOSv2/src/cpu/amd/car/copy_and_run.c trunk/LinuxBIOSv2/src/cpu/amd/car/post_cache_as_ram.c trunk/LinuxBIOSv2/src/cpu/x86/car/copy_and_run.c Log: Change 'ram' to 'RAM' in user-visible output (closes #60). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/LinuxBIOSv2/src/arch/i386/init/crt0.S.lb =================================================================== --- trunk/LinuxBIOSv2/src/arch/i386/init/crt0.S.lb 2006-12-28 12:00:58 UTC (rev 2534) +++ trunk/LinuxBIOSv2/src/arch/i386/init/crt0.S.lb 2007-01-16 11:56:35 UTC (rev 2535) @@ -215,7 +215,7 @@ #if defined(CONSOLE_DEBUG_TX_STRING) && (ASM_CONSOLE_LOGLEVEL > BIOS_DEBUG) .section ".rom.data" -str_copying_to_ram: .string "Copying LinuxBIOS to ram.\r\n" +str_copying_to_ram: .string "Copying LinuxBIOS to RAM.\r\n" str_pre_main: .string "Jumping to LinuxBIOS.\r\n" .previous Modified: trunk/LinuxBIOSv2/src/cpu/amd/car/copy_and_run.c =================================================================== --- trunk/LinuxBIOSv2/src/cpu/amd/car/copy_and_run.c 2006-12-28 12:00:58 UTC (rev 2534) +++ trunk/LinuxBIOSv2/src/cpu/amd/car/copy_and_run.c 2007-01-16 11:56:35 UTC (rev 2535) @@ -23,7 +23,7 @@ uint8_t *src, *dst; unsigned long ilen, olen; - print_debug("Copying LinuxBIOS to ram.\r\n"); + print_debug("Copying LinuxBIOS to RAM.\r\n"); #if !CONFIG_COMPRESS __asm__ volatile ( Modified: trunk/LinuxBIOSv2/src/cpu/amd/car/post_cache_as_ram.c =================================================================== --- trunk/LinuxBIOSv2/src/cpu/amd/car/post_cache_as_ram.c 2006-12-28 12:00:58 UTC (rev 2534) +++ trunk/LinuxBIOSv2/src/cpu/amd/car/post_cache_as_ram.c 2007-01-16 11:56:35 UTC (rev 2535) @@ -53,7 +53,7 @@ set_init_ram_access(); /* So we can access RAM from [1M, CONFIG_LB_MEM_TOPK) */ // dump_mem(DCACHE_RAM_BASE+DCACHE_RAM_SIZE-0x8000, DCACHE_RAM_BASE+DCACHE_RAM_SIZE-0x7c00); - print_debug("Copying data from cache to ram -- switching to use ram as stack... "); + print_debug("Copying data from cache to RAM -- switching to use RAM as stack... "); /* from here don't store more data in CAR */ #if 0 Modified: trunk/LinuxBIOSv2/src/cpu/x86/car/copy_and_run.c =================================================================== --- trunk/LinuxBIOSv2/src/cpu/x86/car/copy_and_run.c 2006-12-28 12:00:58 UTC (rev 2534) +++ trunk/LinuxBIOSv2/src/cpu/x86/car/copy_and_run.c 2007-01-16 11:56:35 UTC (rev 2535) @@ -15,7 +15,7 @@ unsigned long dst_len; unsigned long ilen, olen; - print_debug("Copying LinuxBIOS to ram.\r\n"); + print_debug("Copying LinuxBIOS to RAM.\r\n"); #if !CONFIG_COMPRESS __asm__ volatile (

1 0

[LinuxBIOS] geode LX
by Steve Spano 15 Jan '07

15 Jan '07

Hi There we are getting ready to make a custom Geode LX + CS5336 SBC. It looks like there already is support for this in the LinuxBios - is there a quick FAQ/etc on how to setup the toolchain/configure/etc so we can get a build? Thanks Steve Spano, President Finger Lakes Engineering 607-277-1614 www.fl-eng.com steve(a)flconsult.com

2 2

Re: [LinuxBIOS] MSI K9SD Master-S2R (MS-9185)
by bxshi 15 Jan '07

15 Jan '07

>I will release MCP55 support very soon. We got the approval. >YH That is really good news. I have a MCP55+socket F board half done , with yinghai's code I think I can finish it very soon. then there may be more choices. ;) bxshi

1 0

[LinuxBIOS] Via epia-m2 difficulties
by Kurt André Selbach 15 Jan '07

15 Jan '07

Hi! I'm trying to get a working linuxbios on my Via epia m2 12000, with 1200mhz processor and 512mb ram. The goal is to boot linux from a usbstick (guess i will be using filo and boot the device a uda1) I've managed to extract my videobios image with awardeco and that gave me a videobios file which was exactly 57344byte, how can i apply this to my linuxbios.rom file? The issue is the linuxbios.rom file is allready 256kb, Where would i change the size of this built "rom file" and what should i set it to: I tried setting this: option ROM_SIZE=256*1024 to: option ROM_SIZE=200*1024 Then doing: buildtarget via/epia-m cd via/epia-m/via_epia-m make This gives me this: ... ./buildrom linuxbios.strip linuxbios.rom payload 0x10000 0x12000 payload (41187) + linuxbios (65536) size larger than ROM (73728) size! make[1]: *** [linuxbios.rom] Error 1 ... Any suggestions would be welcome.

5 4

Re: [LinuxBIOS] LinuxBIOS not working...
by sanjay tiwary 15 Jan '07

15 Jan '07

I think i should give u the more details: Southbridge Chip: VIA VT82C686 Following controllers/device are integrated with the bridge: Integrated Super IO Controller - Supports 2 serial ports, IR port, parallel port, and floppy disk controller functions - Two UARTs for Complete Serial Ports Programmable character lengths (5,6,7,8) Even, odd, stick or no parity bit generation and detection Programmable baud rate generator High speed baud rate (230Kbps, 460Kbps) support Independent transmit/receiver FIFOs Modem Control Plug and play with 96 base IO address and 12 IRQ options - One dedicated IR port Third serial port dedicated to IR function IR function either through the two complete serial ports or the third dedicated port Infrared-IrDA (HPSIR) and ASK (Amplitude Shift Keyed) IR - Multi-mode parallel port Standard mode, ECP and EPP support Plug and play with 192 base IO address, 12 IRQ and 4 DMA options - Floppy Disk Controller 16 bytes of FIFO Data rates up to 1Mbps Perpendicular recording driver support Two FDDs with drive swap support Plug and play with 48 base IO address, 12 IRQ and 4 DMA options Sanjay ----- Original Message ---- From: Stefan Reinauer <stepan(a)coresystems.de> To: sanjay tiwary <stiwary20(a)yahoo.com> Cc: linuxbios(a)linuxbios.org Sent: Friday, January 12, 2007 4:23:18 PM Subject: Re: [LinuxBIOS] LinuxBIOS not working... * sanjay tiwary <stiwary20(a)yahoo.com> [070112 07:54]: > Hi Ron/All members of the LinuxBIOS group, > > I am new to the linuxBIOS technology.And wanetd to use the linuxBIOS stuff.But > after creating the rom image and burning the chip, > i was not able to see anything on either on display or on serial console.Can > any one help me getting out of the problem. > I am giving all the details so that you people can make out where am missing? What superio is on the board? -- coresystems GmbH Brahmsstr. 16 D-79104 Freiburg i. Br. Tel.: +49 761 7668825 Fax: +49 761 7664613 Email: info(a)coresystems.de http://www.coresystems.de/ -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios ____________________________________________________________________________________ Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now.

6 5

[LinuxBIOS] MSI K9SD Master-S2R (MS-9185)
by Arvind Seshadri 14 Jan '07

14 Jan '07

Hi, I am looking for a Socket F motherboard that is compatible with LinuxBIOS. The MSI K9SD Master-S2R (MS-9185) seems to be the only one that fits the bill. A couple of questions: 1. Where can I find datasheets for the chipset on this motherboard (Broadcom BCM5785, Broadcom BCM5780)? 2. What is the best place to buy this motherboard? It seems MSI only sells this board in Germany. None of the dealers listed on the MSI Germany webpage seem to carry the board. Thanks, Arvind

5 4

[LinuxBIOS] New DTX motherboard standard from AMD
by Vlad C. 13 Jan '07

13 Jan '07

Hi, AMD has announced a new desktop motherboard standard called DTX that they claim will be a more space and energy efficient than its predecessor, ATX. DTX motherboards will be smaller (about the size of a micro-ATX), but will try to maintain compatibility with existing hardware. More information about them can be found here: http://hardware.slashdot.org/hardware/07/01/12/1940239.shtml It would be great if LinuxBIOS will run on these motherboards from their initial release. One of the stated aims of DTX is to increase upgradeability of smaller (ie. laptop) components, which are at present highly integrated and incompatible with other parts. LinuxBIOS, with its open design, would complement this goal very well by enabling the community to help fix compatibility problems that may arise. In the end, consumers will benefit from having more forward-compatible hardware. Vlad ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com

1 0

← Newer
1
...
6
7
8
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot January 2007