coreboot

coreboot@coreboot.org

6 participants
39707 discussions

serial console problems
by Alexander Amelkin 16 Mar '03

16 Mar '03

Hello! I already asked, but nobody answered my question. I'm having problems with the serial console when booting LinuxBIOS on a pcchips m787cl+ motherboard. The serial works for output (I can see what the box says) but doesn't for input (I can't login from the serial console). If I boot the same kernel with the same parameters (console=ttyS0,9600n8) using the original motherboard's BIOS (AMI), I don't have any problems at all. Any suggestions? With best regards, Alexander mailto:spirit@reactor.ru

3 2

compiling etherboot
by Alessio Sangalli 16 Mar '03

16 Mar '03

Hi. I'm trying to compile etherboot for linuxbios to boot an image on a ide device. I downloaded both version 5.0.9 and 5.1.7. Would you tell me which targets should I make? What about file system support? bye bye thank you as -- How to build a lirc receiver http://www.manoweb.com/alesan/lirc

1 0

Patch to flash_rom
by SONE Takeshi 16 Mar '03

16 Mar '03

Hi, I modified the flash_rom program a little and it might be useful for others. - Add "enable" for VIA VT8231 (southbridge of EPIA board) This does same thing as what is in src/mainboard/via/epia/README. (Btw, I downloaded the datasheet for VT8231 from here: http://www.google.com/search?q=vt8231+application%2Fpdf It's publically online ;-) - Fixed segfault when no "enable" is defined for a board. - Fixed delay calibration so it really finishes in a second (original code takes up to 100 seconds theoretically, >10 seconds on my box) - Support for -r (read), -w (write), and -v (verify). Writing is not really tested since I don't have my BIOS Savior yet. Looking forward to trying out LinuxBIOS on my box. Thanks for the great work. -- Takeshi Index: flash_rom.c =================================================================== RCS file: /cvsroot/freebios/freebios/util/flash_and_burn/flash_rom.c,v retrieving revision 1.16 diff -u -r1.16 flash_rom.c --- flash_rom.c 28 Feb 2003 17:21:37 -0000 1.16 +++ flash_rom.c 12 Mar 2003 14:03:11 -0000 @@ -136,6 +136,9 @@ new = old | 1; + if (new == old) + return 0; + ok = pci_write_byte(dev, 0x4e, new); if (ok != new) { @@ -146,6 +149,28 @@ return 0; } +int +enable_flash_vt8231(struct pci_dev *dev, char *name) { + unsigned char old, new; + int ok; + + old = pci_read_byte(dev, 0x40); + + new = old | 0x10; + + if (new == old) + return 0; + + ok = pci_write_byte(dev, 0x40, new); + + if (ok != 0) { + printf("tried to set 0x%x to 0x%x on %s failed (WARNING ONLY)\n", + old, new, name); + return -1; + } + return 0; +} + struct flashchip * probe_flash(struct flashchip * flash) { int fd_mem; @@ -227,8 +252,8 @@ timeusec = 1000000 * (end.tv_sec - start.tv_sec ) + (end.tv_usec - start.tv_usec); fprintf(stderr, "timeusec is %d\n", timeusec); - count *= 100; - if (timeusec < 1000000) + count *= 2; + if (timeusec < 1000000/3) continue; ok = 1; } @@ -260,6 +285,7 @@ {0x1, 0x1, "sis630 -- what's the ID?", enable_flash_sis630}, {0x8086, 0x2480, "E7500", enable_flash_e7500}, + {0x1106, 0x8231, "VT8231", enable_flash_vt8231}, }; int @@ -291,10 +317,25 @@ } /* now do the deed. */ - enable->doit(dev, enable->name); + if (enable) { + printf("Enabling flash write on %s...", enable->name); + if (enable->doit(dev, enable->name) == 0) + printf("OK\n"); + } return 0; } +void usage(const char *name) +{ + printf("usage: %s [-rwv] [file]\n", name); + printf("-r: read flash and save into file\n" + "-w: write file into flash (default when file is specified)\n" + "-v: verify flash against file\n" + " If no file is specified, then all that happens\n" + " is that flash info is dumped\n"); + exit(1); +} + int main (int argc, char * argv[]) { @@ -302,12 +343,36 @@ unsigned long size; FILE * image; struct flashchip * flash; - - if (argc > 2){ - printf("usage: %s [romimage]\n", argv[0]); - printf(" If no romimage is specified, then all that happens\n"); - printf(" is that flash info is dumped\n"); + int opt; + int read_it = 0, write_it = 0, verify_it = 0; + char *filename = NULL; + while ((opt = getopt(argc, argv, "rwv")) != EOF) { + switch (opt) { + case 'r': + read_it = 1; + break; + case 'w': + write_it = 1; + break; + case 'v': + verify_it = 1; + break; + default: + usage(argv[0]); + break; + } } + if (read_it && write_it) { + printf("-r and -w are mutually exclusive\n"); + usage(argv[0]); + } + + if (optind < argc) + filename = argv[optind++]; + + printf("Calibrating timer since microsleep sucks ... takes a second\n"); + myusec_calibrate_delay(); + printf("OK, calibrated, now do the deed\n"); /* try to enable it. Failure IS an option, since not all motherboards * really need this to be done, etc., etc. It sucks. @@ -320,25 +385,35 @@ } printf("Part is %s\n", flash->name); - if (argc < 2){ + if (!filename){ printf("OK, only ENABLING flash write, but NOT FLASHING\n"); return 0; } size = flash->total_size * 1024; - - if ((image = fopen (argv[1], "r")) == NULL) { - perror("Error opening image file"); - exit(1); - } - buf = (char *) calloc (size, sizeof(char)); - fread (buf, sizeof(char), size, image); - printf("Calibrating timer since microsleep sucks ... takes a second\n"); - myusec_calibrate_delay(); - printf("OK, calibrated, now do the deed\n"); + if (read_it) { + if ((image = fopen (filename, "w")) == NULL) { + perror("Error opening image file"); + exit(1); + } + printf("Reading Flash..."); + memcpy(buf, (const char *) flash->virt_addr, size); + fwrite(buf, sizeof(char), size, image); + fclose(image); + printf("done\n"); + } else { + if ((image = fopen (filename, "r")) == NULL) { + perror("Error opening image file"); + exit(1); + } + fread (buf, sizeof(char), size, image); + fclose(image); + } - flash->write (flash, buf); - verify_flash (flash, buf, /* verbose = */ 0); + if (write_it) + flash->write (flash, buf); + if (verify_it) + verify_flash (flash, buf, /* verbose = */ 0); return 0; }

9 20

New version of DOC Millennium MD2802-D08
by Andrew Ip 16 Mar '03

16 Mar '03

MD2802-D08 is the new version of MD2800-D08. Basically it is the same with newer packing, and it is working with LinuxBIOS!!! -Andrew -- Andrew Ip Email: aip(a)cwlinux.com Tel: (852) 2542 2046 Fax: (852) 2542 2036 Mobile: (852) 9201 9866 Cwlinux Limited Unit 202B 2/F Lai Cheong Factory Building, 479-479A Castle Peak Road, Lai Chi Kok, Kowloon, Hong Kong. Tel: (852)2542 2046 Fax: (852)2542 2036 For public pgp key, please obtain it from http://www.keyserver.net/en.

1 0

Looking for datasheet of Sis chipset
by Charlie Song 14 Mar '03

14 Mar '03

Hello all, Could anyone provide the datasheet of SiS chipset that supports Intel Pentim 4/3 ? Thanks, Charlie

1 0

problem with udelay solved - romimage too big
by Alessio Sangalli 14 Mar '03

14 Mar '03

Hi, mucking with the source cde and with configuration samples I've solved the compile problem I wrote about yesterday night (udelay) Now I can get a romimage file. I plan to burn this file inside the normal flash of my pcchips 810 board to boot from IDE (hard disk). However, the file romimage is too big! I would have expected a 256KB file, but I obtain a 1.4MB one: $ ll -h payload.block linuxbios.rom romimage -rw-rw-r-- 1 alesan alesan 64k Mar 14 13:31 linuxbios.rom -rw-rw-r-- 1 alesan alesan 1.3M Mar 14 13:31 payload.block -rw-rw-r-- 1 alesan alesan 1.4M Mar 14 13:31 romimage What am I doing wrong? This is the config file: target rom mainboard pcchips/m810lmr cpu k7 option CONFIG_UDELAY_TSC=1 option VIDEO_CONSOLE=1 option SERIAL_CONSOLE=1 option DEFAULT_CONSOLE_LOGLEVEL=6 option SERIAL_POST=1 option ENABLE_MII=1 option MUST_ENABLE_FLOPPY=1 option HAVE_FRAMEBUFFER=1 option SMA_SIZE=0x80 option BOOT_IDE=1 option IDE_BOOT_DRIVE=0 option ONE_TRACK=32 biosbase 0xffff0000 linux /usr/src/linux commandline root=/dev/hda1 console=ttyS0,115200 console=tty0 bye bye thank you as -- How to build a lirc receiver http://www.manoweb.com/alesan/lirc

6 9

Newbie question
by Yann POUPET 14 Mar '03

14 Mar '03

Hi, I've read a lot of posts, but haven't found what I'm looking for. I think I've understood that linuxBios is only there to be able to boot another Linux. Is it possible to boot the kernel directly in (from?) the bios then launching init, mouting HDs... I mean, is there a way to do as if there where no bios on a pc, decompressing the kernel just after power-on, and going on? I'd like to do this, and 8MBytes millenium doc could maybe help me. Actually I just need a fast booting system. Hope this is not too much stupid question...

3 3

Price detail of linuxBios
by instec＠vsnl.net 13 Mar '03

13 Mar '03

Hi, Attached pls find our company profile for your reference. We are developing an 'PVR' for which we need LinuxBios. Would like to know Price of the same. The 'PVR' contains x86 Processor. Our Client is from California , USA and has come to us through our US office. We expect the production to take place in Taiwan or Indonesia and estimated volume is 10K units per month Feel free to call me if you require any further info. Thanks V.Suresh Kumar Init systems II floor - Asoka plaza #483 , Dr.Nanjappa road Gandhi puram Coimbatore INDIA- 641 018 Ph : 91 422 223 6466 fax : 91 422 223 6755

2 1

EPIA HOWTO
by Andrew Ip 13 Mar '03

13 Mar '03

I have just checked in a HOWTO for EPIA. Thanks to Mark Wilkinson for providing us this document. -Andrew -- Andrew Ip Email: aip(a)cwlinux.com Tel: (852) 2542 2046 Fax: (852) 2542 2036 Mobile: (852) 9201 9866 Cwlinux Limited Unit 202B 2/F Lai Cheong Factory Building, 479-479A Castle Peak Road, Lai Chi Kok, Kowloon, Hong Kong. Tel: (852)2542 2046 Fax: (852)2542 2036 For public pgp key, please obtain it from http://www.keyserver.net/en.

1 0

Ram initialization and small c.
by ebiederman＠lnxi.com 13 Mar '03

13 Mar '03

Years ago when C was young and implementations were not readily available people compilers for subsets of C and called then small C compilers. Currently one of the greatest challenges in LinuxBIOS is to write ram initialization code. On x86 this is all done in 8 general purpose registers. And it takes about a 1000 lines of assembly per memory controller, to do a good job and handle all of the auto-configuration cases. Debugging the assembly is bad as frequently adding the debug code breaks the code we are trying to debug. Additionally there is no code reuse between the two binaries that make up LinuxBIOS as one is in C and the other in assembly. By this point I have enough practice I am good at writing the assembly code, that I think it hardly matters. But I have seen several proficient coders just grind to a halt when confronted with miles of assembly. So what I propose is to write a small C compiler for LinuxBIOS. Various reports from ages past put it at about a man-month of effort to get the first version going. And it may be better than that as there are a couple of places I can copy code from. tcc, lcc, gcc, and other small c projects. Up until this point all C compilers have had an assumption that you can have a stack. And most simple C compilers have kept none of the data structures needed to do inline and similar optimizations that are necessary when you don't have ram. So I think it is easiest to build up something very simple from scratch. That is the route I am going to try. No promises, but I should start a trial implementation soon. Ron. I am going to need to do a branch soon as I do the Hammer port and integrate a small C compiler. And I want to make some clean fixes and remove some of the backwards compatibility cruft, and the linuxbios 1.0 code base is an inappropriate place to target. It should be possible to roll in most of the improvements into the 1.0 codebase, but that will just increase the clutter of the codebase. Eric

10 48

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