coreboot

coreboot@coreboot.org

7 participants
39699 discussions

COMMIT: intel/Clearwater
by steven james 26 Oct '02

26 Oct '02

Greetings, Support for the Intel Clearwater mainboard has been committed. Clearwater is a dual PIV Xeon board based on the E7500 chipset. G'day, sjames -- -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 -----------------------------------------------------------------------

3 3

Building LinuxBIOS in Debian Potato
by steven james 26 Oct '02

26 Oct '02

Greetings, If anyone (besides me) is still using a Debian Potato based development machine, here's quick instructions to get things going: There are a few places that call for a newer version of binutils (at least to handle the use of the movnti instruction in PIV builds) Building Woody's binutils package from source will take care of it. If you prefer not to change everything, The minimum impact approach seems to be: 1.fetch binutils source package from Woody. 2.unpack and apply Debian patch 3. chmod +x debian/rules 4. cd build-tree/binutils-2.12.90.0.1 do configure and make in opcodes. do configure, make, and make install in libiberty and bfd do configure --enable-shared, make, make install in binutils, and gas All of that will go into /usr/local cd /usr/bin mv as as.old (just in case) ln -s /usr/local/bin/as as LinuxBIOS will now build successfully. G'day, sjames -- -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 -----------------------------------------------------------------------

1 0

RFC tagged payload
by steven james 25 Oct '02

25 Oct '02

Greetings, I've been working with a tagging system so that multiple payloads in firmware can be selected from serial at boot time. The scheme adds a 16 byte tag block in front of each payload containing a $TAG$ signature, additional block count, a payload length (optional, may be 0), and a name string. The idea is to search for tags in the ROM, present the name strings in a list and allow selection of a particular target. The stream is then positioned just past the tag and passed to elfboot. changes: elfboot no longer calls stream->init(), it presumes that has been done already. add stream methods: searchtags gettags loadtag search tags performs the search and specifies the neded buffer size to hold the result. gettags loads the tags into a provided buffer for presentation loadtag positions the stream just after the selected tag index (0 based) for backwards compatability: Where no tags are found, the stream is positioned at the beginning where the stream->searchtags == NULL, presume the stream object doesn't support tags. Just call init and pass it to elfboot. Yes, No, Comments? G'day, sjames -- -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 -----------------------------------------------------------------------

2 1

movnti
by steven james 25 Oct '02

25 Oct '02

Greetings, Recent ramtest and spotcheck.inc use the movnti instruction to bypass the cache when writing. gas 2.9.5 handles everything but that instruction. options: 1. don't use movnti 2. make it configurable 3. shut up and update binutils :-) Comments? G'day, sjames -- -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 -----------------------------------------------------------------------

3 3

root file system where
by OliverArnold＠via.com.tw 25 Oct '02

25 Oct '02

Hello World, I try to set up a LinuxBIOS System. What i really can not understand is the following: When I Flash the root filesystem into the BIOS Flash rom, where do i tell the kernel to mount it? How does that work? Thank you Oliver

1 0

RE: AW: DOC vs. IDE
by McMechan, James 24 Oct '02

24 Oct '02

Actually it was worse even in 2.4, the flash detection will disable the other device e.g. hda=harddisk hdb=flash core probes hda prints out hda detection everything seems fine core probes hdb prints out hdb detection *** silently disables hda *** system tries to boot from hda dies as device is not present. user goes insane because it is printed in the log as being detected see about line 169 of linux-2.4.19/drivers/ide/ide-probe.c I have a system with soldered in flash that with a hard disk is hdb I have to pass hdb=noprobe to prevent that system from failing The comments indicate that this is put in to prevent wasting time on probing non existent slave device but it is disabling the master device if the slave is flash :( > ---------- > From: Richard A. Smith > Reply To: Richard A. Smith > Sent: Wednesday, October 23, 2002 14:28 > To: linuxbios(a)clustermatic.org > Subject: Re: AW: DOC vs. IDE > > On Wed, 23 Oct 2002 14:28:23 -0600 (MDT), Ronald G Minnich wrote: > > > On Wed, 23 Oct 2002, Christopher Bergeron wrote: > > > > > That actually sounds like a brilliant idea. I wonder if anyone on the > > > list can confirm performance... does the CFcard appear as a standard > IDE > > > disk or is there a driver or anything necessary? > > > > we're doing it here on the PCM-5823-A2 geode cards. We use CF as > /dev/hdc, > > there is no /dev/hd1. Works fine. > > > > I'll pipe in a little bit of personal experience here. If you are > _just_ using a CF with an IDE adapter then all is well and things > will work great. > > During bringup and debug though its nice to have a big HD with a full > linux distribution on on it so you can develope on your target. > > However if you are using a CF _and_ a normal IDE drive you may run > into a gotcha. In the 2.2 linux IDE code there are clauses that if a > CF device is dectected on hda it will NOT probe for hdb. Same goes > for hdc and hdd. There is no output telling you its skipping it > either. Apparently there were some early CF devices that did some > funky stuff with the diag signal (drive dection) and Andre (the 2.2 > IDE maintainer) chose to blacklist all CF devices. > > The fix is to feed the kernel some parameter like ide0=flash or > something similar to make it go ahead and probe. > > I haven't looked at the 2.4.x IDE code so I don't know if it carried > over or not. > > But if you mysteriously don't have an hdb with a CF hooked up in your > system go check the IDE probing code before you pull you hair out > trying to figure out whats wrong with your hardware like I did. > > -- > Richard A. Smith Bitworks, Inc. > rsmith(a)bitworks.com 479.846.5777 x104 > > Sr. Design Engineer http://www.bitworks.com > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > >

1 0

Re: AW: DOC vs. IDE
by Dave Dworin 24 Oct '02

24 Oct '02

I doubt if CF is reliable to replace IDE disks. I own a CF digital camera and have experienced data loss. It seems that data loss/file corruption is quite common on CF. Any different experience? Dave >From: "Richard A. Smith" <rsmith(a)bitworks.com> >Reply-To: "Richard A. Smith" <rsmith(a)bitworks.com> >To: "linuxbios(a)clustermatic.org" <linuxbios(a)clustermatic.org> >Subject: Re: AW: DOC vs. IDE >Date: Wed, 23 Oct 2002 16:28:28 -0500 > >On Wed, 23 Oct 2002 14:28:23 -0600 (MDT), Ronald G Minnich wrote: > > > On Wed, 23 Oct 2002, Christopher Bergeron wrote: > > > > > That actually sounds like a brilliant idea. I wonder if anyone on the > > > list can confirm performance... does the CFcard appear as a standard >IDE > > > disk or is there a driver or anything necessary? > > > > we're doing it here on the PCM-5823-A2 geode cards. We use CF as >/dev/hdc, > > there is no /dev/hd1. Works fine. > > > >I'll pipe in a little bit of personal experience here. If you are >_just_ using a CF with an IDE adapter then all is well and things >will work great. > >During bringup and debug though its nice to have a big HD with a full >linux distribution on on it so you can develope on your target. > >However if you are using a CF _and_ a normal IDE drive you may run >into a gotcha. In the 2.2 linux IDE code there are clauses that if a >CF device is dectected on hda it will NOT probe for hdb. Same goes >for hdc and hdd. There is no output telling you its skipping it >either. Apparently there were some early CF devices that did some >funky stuff with the diag signal (drive dection) and Andre (the 2.2 >IDE maintainer) chose to blacklist all CF devices. > >The fix is to feed the kernel some parameter like ide0=flash or >something similar to make it go ahead and probe. > >I haven't looked at the 2.4.x IDE code so I don't know if it carried >over or not. > >But if you mysteriously don't have an hdb with a CF hooked up in your >system go check the IDE probing code before you pull you hair out >trying to figure out whats wrong with your hardware like I did. > >-- >Richard A. Smith Bitworks, Inc. >rsmith(a)bitworks.com 479.846.5777 x104 >Sr. Design Engineer http://www.bitworks.com > > >_______________________________________________ >Linuxbios mailing list >Linuxbios(a)clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios _________________________________________________________________ Unlimited Internet access for only $21.95/month. Try MSN! http://resourcecenter.msn.com/access/plans/2monthsfree.asp

6 6

PIC question. (fwd)
by adam＠www.missl.cs.umd.edu 24 Oct '02

24 Oct '02

[PS: Can I somehow tell mailman to accept my email from multiple addresses?] hello I'm trying to set "bios classic/dos" like state on the winfast 6300max/sis630 motherboard. one of the issues I'm having is that it seems that interrupt 9 (keyboard) is not beging tiggered. (this is after linuxbios finish booting and I start bochs bios). Initially I have suspected that the PIC in the sis630 is not getting programmed. However, going over boch's bios sources I found out that it does DO program PIC..so it is not the issue here. (relevant code at end of email). Thus the question is : What is the extra step I'm missing that has to be run after linuxbios finish but before attempting to program PIC for bios/dos style interrupt mapping? Ideas? ;; PIC mov al, #0x11 ; send initialisation commands out 0x20, al out 0xa0, al mov al, #0x08 out 0x21, al mov al, #0x70 out 0xa1, al mov al, #0x04 out 0x21, al mov al, #0x02 out 0xa1, al mov al, #0x01 out 0x21, al out 0xa1, al -- Adam http://www.eax.com The Supreme Headquarters of the 32 bit registers

9 23

via information
by OliverArnold＠via.com.tw 24 Oct '02

24 Oct '02

hey, nice to see, that you are working on projects wirth our epia mainboard. what information do you need for the port? perhaps i can organise something ... oliver

1 0

(no subject)
by hill91 24 Oct '02

24 Oct '02

1 0

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