coreboot April 2007

coreboot@coreboot.org

76 participants
281 discussions

[LinuxBIOS] r2610 - trunk/LinuxBIOSv2/util/flashrom
by svn＠openbios.org 14 Apr '07

14 Apr '07

Author: stepan Date: 2007-04-14 18:32:59 +0200 (Sat, 14 Apr 2007) New Revision: 2610 Modified: trunk/LinuxBIOSv2/util/flashrom/flashrom.c trunk/LinuxBIOSv2/util/flashrom/layout.c Log: Exit on return code of read_layout and print error message to stderr instead of stdout (trivial) Signed-off-by: Stefan Reinauer <stepan(a)coresystems.de> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/LinuxBIOSv2/util/flashrom/flashrom.c =================================================================== --- trunk/LinuxBIOSv2/util/flashrom/flashrom.c 2007-04-12 01:23:12 UTC (rev 2609) +++ trunk/LinuxBIOSv2/util/flashrom/flashrom.c 2007-04-14 16:32:59 UTC (rev 2610) @@ -303,7 +303,8 @@ break; case 'l': tempstr=strdup(optarg); - read_romlayout(tempstr); + if (read_romlayout(tempstr)) + exit(1); break; case 'i': tempstr=strdup(optarg); Modified: trunk/LinuxBIOSv2/util/flashrom/layout.c =================================================================== --- trunk/LinuxBIOSv2/util/flashrom/layout.c 2007-04-12 01:23:12 UTC (rev 2609) +++ trunk/LinuxBIOSv2/util/flashrom/layout.c 2007-04-14 16:32:59 UTC (rev 2610) @@ -106,7 +106,8 @@ romlayout=fopen (name, "r"); if(!romlayout) { - printf("Error while opening rom layout (%s).\n", name); + fprintf(stderr, "ERROR: Could not open rom layout (%s).\n", + name); return -1; }

1 0

[LinuxBIOS] IDE become readonly, why?
by Beneo 13 Apr '07

13 Apr '07

Hi all, I was using LinuxBIOS to boot Linux from IDE from a Broadcom HT,1000 south bridge based platform , I encounter an issue which is hard to understand. I hope somebody can give me some insight. During boot, Linux stoped at the point that it displayed a message: "Configuring kernel parameters: [ OK ]" then I pressed "CTRL-C", Linux continue to boot, but display a message: "Starting automount:Cannot create temp file /tmp/autofs.meQYNM, could not make temp file" then Linux boot Skipped rest of initialization, like probe the network and etc. but Linux did give me a login prompt, I can login using root, but I cannot write any file at root directory, It appears to me Entire Linux file system becomes readonly. Phoenix BIOS came with that board doesn't have this issue, so I know it should be LinuxBIOS related. I just don't know why. Does anybody know anything about this issue? Thanks Beneo ---- dump from Linux boot. INIT: version 2.84 booting Welcome to Red Hat Linux Press 'I' to enter interactive startup. Mounting proc filesystem: [ OK ] Unmounting initrd: [ OK ] Configuring kernel parameters: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Starting pcmcia: [ OK ] Starting automount:Cannot create temp file /tmp/autofs.meQYNM could not make temp file INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: Id "3" respawning too fast: disabled for 5 minutes INIT: Id "4" respawning too fast: disabled for 5 minutes INIT: Id "5" respawning too fast: disabled for 5 minutes INIT: Id "6" respawning too fast: disabled for 5 minutes Red Hat Linux release 9 (Shrike) Kernel 2.4.20-8smp on an i686 (none) login:

9 30

[LinuxBIOS] Support for Tyan s2915 or s2927
by Arvind Seshadri 13 Apr '07

13 Apr '07

Hi, I am looking into building a personal workstation around the Tyan S2915 or the Tyan S2927 for LinuxBIOS hacking. I have been following the mailing list since January when Yinghai Lu posted a huge patch with support for the Tyan S2912, among other boards. >From Tyan's webpage it seems that the S2927, like the S2912, uses the nVIDIA MCP55 southbridge. However, the Super I/O chip on the S2927 is a SMSC SCH5017 and not the Winbond W83627HF found on the S2912. The S2915 uses the nVIDIA NFP3600 + NPF3050 as the southbridge and the SMSC 5307 Super I/O controller. Would Yinghai's patch support either of these two boards? Thanks, Arvind

5 5

[LinuxBIOS] GA-M57SLI-S4 bios programming
by ST 13 Apr '07

13 Apr '07

Hi I am still puzzled how the second flash chip is to be used on the GA-M57SLI-S4 board. As Peter mentioned LPC is used on this board. Would it be enough to use the flash chips (for programming and reading) to just disable one chip with the #init signal? It seems as if only one of the chips gets the #init to low, the other one will stay in reset mode and will keep its I/O pins in Z state? Thanks ST

3 3

[LinuxBIOS] how about the support of Tyan s2915 in LinuxBIOS
by Ning (Michael) Qu 12 Apr '07

12 Apr '07

Hi, all, We want to use LinuxBIOS on Tyan s2915. Is there anyone who has similiar experience? Is it well supported by LinuxBIOS? v1 or v2? Thanks very much! Best, Michael

2 2

Re: [LinuxBIOS] r2602 - trunk/LinuxBIOSv2/util/getpir
by Uwe Hermann 12 Apr '07

12 Apr '07

On Wed, Apr 11, 2007 at 08:44:43PM +0200, svn(a)openbios.org wrote: > Jeremy Jackson wrote: > I'm guessing nobody has tried compiling it with 64bit userspace? > > Patch makes it compile cleanly and stops a "SEGV instead of working" > issue. > > I also added a few checks for errors on system calls. > > Signed-off-by: Jeremy Jackson <jerj(a)coplanar.net> > > Reworked and > Acked-by: Stefan Reinauer <stepan(a)coresystems.de> I think this should either be Signed-off-by: Stefan Reinauer <stepan(a)coresystems.de> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> (sign-off because you modified the code, acked-by because you acked it and it needs an ack before it can be committed) or: You repost the modified patch for review (if your modifications are nontrivial), with the original sign-off and your new sign-off and waiting for an ack: Signed-off-by: Jeremy Jackson <jerj(a)coplanar.net> Signed-off-by: Stefan Reinauer <stepan(a)coresystems.de> (See also my other post, answering Peter's question from a few days ago) > all: getpir checkpir > + ./checkpir Don't do this please. If I type 'make' I don't expect the build process to _run_ the resulting binary for me (won't work anyways as it needs root access and you usually don't compile as root). > +irq_tables.c: getpir > + ./getpir See above. > -test: checkpir > - ./checkpir ;\ > - exit 0; An extra target such as this ('test' or 'run' or so) would be fine, though. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org

4 5

Re: [LinuxBIOS] GA-M57SLI-S4 dual bios pins was Re: New with a GA-M57SLI-S4
by Beth 12 Apr '07

12 Apr '07

Hi all again (hi ST, yes I am Jose, Beth is a long story :D, some day ...). Well one week of holidays, half other with a lot of work and some days without batteries on the multimeter ..., I am back. Well I am a bit "disconnected", but, ST are you still interested on that I check the pins of the second socket?. What about your discoveries about the #init pin? And talking about the #init, guys, have you seen the mail from Luis Correia??: >after some time being absent from here while attending o some other >pressing issues, i'm back to LinuxBIOS :) >My NOVA-4899R needs a proper bios and I'm confident that this time it >would get better. >But as always, problem is swapping the BIOS with enough confidence. >After ruining onf my my precious BIOS chips, I decided on a radical >approach. >Here is the photo (sorry for the hosting), and the explanation follows: >http://img156.imageshack.us/img156/7942/detail01hd8.jpg >This is composed of a BIOS with a PLCC socket soldered on top (all >pins except #CE) >Then, the #CE signal is intercepted and routed to a switch, which in >turn selects the upper or lower chip. >After the first boot and using uniflash as a detecting software for >the parts, only one of the chips was correctly identified. Then it >struct me that while one chip was connected to the controller, the >other had the pin 'free floating'. This was solved by pulling the two >#CE pins from the flash devices to +5V. >This is a very dumb rig, but hey, it works. >I haven't flashed any on the chips yet, but now uniflash does detect >them correctly. >I'll be offline until the 20th but after that i'll try to post more >detailed pictures of it, along with a proper schematics. >Thanks for listeing to all this crap :) >Luis Correia It's like my friend's idea but correctly done (I didn't realized that leaving vcc out will leave the pins "floating"). It seems to work, we don't have #ce pin, but will work on the same way our #init pin. Yesterday I received the new bios chip and a plcc socket so I will try it, first if you give me the ok (jejeje), I must find from where the #pin comes, cut and insert the switch to the chips ... Another thing, ST, I bought the chip, an extraction tool and a socket from http://bios-repair.co.uk/ , I had a very fluid communication and no problems at all with Paul. And, nothing more, see you. Regards.

2 3

Re: [LinuxBIOS] GA-M57SLI-S4 dual bios pins was Re: New with a GA-M57SLI-S4
by ST 12 Apr '07

12 Apr '07

Hi Beth Am Donnerstag, 12. April 2007 14:17 schrieben Sie: > Hi all again (hi ST, yes I am Jose, Beth is a long story :D, some day ...). Nice hearing from you :-) > Well I am a bit "disconnected", but, ST are you still interested on > that I check the pins of the second socket?. Yes! Especially if you could check the Pins where i have written Error? or s.t. like that. Please take a look at: http://private.vlsi.informatik.tu-darmstadt.de/st/dual_bios_GA-m57SLI-S4.jpg and read my mail from the 29.03.2007 00:23:"GA-M57SLI-S4 dual bios pins was Re: New with a GA-M57SLI-S4". It would be really nice if you could recheck: * all the "Error?" pins * If #init is connected to some of the T1X or T2X pins (labeling according to the linked image above). * If any of the T3X or T4x pins is really not connected to the pads / flash. * If any of the "Watchdog" pins are connected to any of the TXX pins. > What about your discoveries about the #init pin? See bullet point #1 in the above list. > Another thing, ST, I bought the chip, an extraction tool and a socket > from http://bios-repair.co.uk/ , I had a very fluid communication and > no problems at all with Paul. Mh, ok. I've got an PLCC32 socket but no bios chip right now :-(. Thanks ST

1 0

[LinuxBIOS] Questions about softVG in olpc??
by Hao Li 12 Apr '07

12 Apr '07

Hi all, I am quite confused about how olpc's codes initialize VGA card. As far as I know, olpc will use softVG vsm (part of VSA) to initialize hardware and provide Interfaces to VGABIOS. But in the olpc's codes I only see a function graphics_init() to pass parameters to softVG. Are there any other functions relate to VGA initialization? Need I dump a VGABIOS image from Linux using softVG and use emulator run that image? Thanks.

1 0

Re: [LinuxBIOS] r2607 - in trunk/LinuxBIOSv2: src/mainboard/artecgroup/dbe61 src/mainboard/technologic/ts5300 targets/technologic/ts5300
by Indrek Kruusa 12 Apr '07

12 Apr '07

Ühel kenal päeval (neljapäev 12 aprill 2007 3:28 am) kirjutas svn(a)openbios.org: > Author: stepan > Date: 2007-04-12 02:28:32 +0200 (Thu, 12 Apr 2007) > New Revision: 2607 > > Modified: > trunk/LinuxBIOSv2/src/mainboard/artecgroup/dbe61/Options.lb > trunk/LinuxBIOSv2/src/mainboard/technologic/ts5300/Options.lb > trunk/LinuxBIOSv2/targets/technologic/ts5300/Config-abuild.lb > trunk/LinuxBIOSv2/targets/technologic/ts5300/Config.lb > Log: > Fix two boards broken by the large patches of late. > > artecgroup/dbe61 > Add CONFIG_COMPRESSED_PAYLOAD_NRV2B to Options.lb since it's used in > Config.lb. > Change default for CONFIG_PCI_ROM_RUN to 1 so VGA ROM can run. I haven't done testing yet but thanks anyway! Indrek

1 0

← Newer
1
...
11
12
13
14
15
16
17
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot April 2007