coreboot

coreboot@coreboot.org

10 participants
39710 discussions

customization
by mannitol 23 Oct '03

23 Oct '03

I have not yet attempted to set up a linux bios. From the guides that I've skimmed through so far I think I shouldn't have too much trouble. I was wondering what kinds of customization options are included. I would like to display a bitmap as the bios loads and hide any messages that would normally be displayed. I know, of course, that this can be done. Unfortunatly I am not much of a programmer. Is there a relatively easy way to do this? Any help would be appreciated.

2 1

AMD64: Something's missing?
by Stefan Reinauer 22 Oct '03

22 Oct '03

Building the Quartet target with latest CVS I get: raminit.c:2378.43: is_cpu_pre_c0 undeclared I'll look into it.. Stefan -- Architecture Team SuSE Linux AG

6 15

RE: AMD64: Something's missing?
by Alan Mimms 22 Oct '03

22 Oct '03

One thing that encryption in the bootstrap CAN do is prevent Trojan attacks against the kernel image. If attackers can't find out what the encryption key is they can't create a substitute Trojan kernel. It plugs a hole. Alan Mimms, Senior Architect F5 Networks, Inc. Spokane Development Center Liberty Lake, Washington v: 509-343-3524 f: 509-343-3501 -----Original Message----- From: SONE Takeshi [mailto:ts1@tsn.or.jp] Sent: Wednesday, October 22, 2003 2:18 AM To: Evan Langlois Cc: linuxbios(a)clustermatic.org Subject: Re: AMD64: Something's missing? On Tue, Oct 21, 2003 at 10:26:01PM +0200, Evan Langlois wrote: > > > EtherBoot can boot lots of things from the network or an IDE hard disk. > > FILO can boot from IDE hard disk, IDE CDROM, floppy, and maybe more? 9load > > I don't know much about except that it is used to load the plan9 kernel. > > I don't know much about FILO. Can anyone comment on its compatibility with > the LILO graphical features (displaying graphical menus/splash screens), and > is there any support available for encrypted filesystems? FILO is not aimed at being compatible with LILO. > Assuming FILO works like LILO, and doesn't know about filesystems, I'm > assuming encryption would be difficult, and it might therefore be best to > chain-load another boot-loader, but I'd want the encryption keys to be in the > ROM to make it as difficult as possible to get to them. FILO has filesystem routines borrowed from GRUB, so it works like GRUB rather than LILO. > Encryption in the BIOS itself may be a positive feature, not just for > corporate users that want to protect their IP, but laptop users and such (in > which case the key would be asked for on boot) that don't want sensitive > information leaking out just because a laptop was stolen. Encryption in boot process doesn't make sense to me. What you want to protect is the data in the storage, not the boot image (kernel). Encryption of the storage is OS's bussiness, and the OS will ask you the password before decrypting any data. -- Takeshi _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

[COMMIT] romcc-0.37
by ebiederman＠lnxi.com 22 Oct '03

22 Oct '03

Ok. Non inline function calls are trickier than I expected. My intuition said I just needed to tweak the generated intermediate code and I could reuse all of my optimizing back end. In almost all cases my back end looks at the code generated declares it spaghetti and refuses to compile it. However I did manage a lot of good general cleanups. I believe I have fix the problem with reading ints instead of bytes from structures. I have optimized the code somewhat so sub word size loads can now be into any of the 8 general purpose registers. I have converted practically all the compile time options into run time switches so the code is a little cleaner and more configurable. Before I return to working on non inlining I need to step back and think some more to see which technique will work best. Either improving my code analysis algorithms, or compiling the functions separately and then inserting calls. There are pluses and minuses to both techniques. Hopefully I will be a little more active now that I have come to a stopping place. Eric

1 0

FW: Forth
by Gregg C Levine 21 Oct '03

21 Oct '03

Hello (again) from Gregg C Levine Folks, take a look at the forwarded message below my signature. It seems to me, that it was spawned from my messages discussing the OpenBIOS kernel. I am inviting advice, and comment. I have responded twice to the person, but so far no replies. ------------------- Gregg C Levine hansolofalcon(a)worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda ) -----Original Message----- From: werty(a)swissinfo.org [mailto:werty@swissinfo.org] Sent: Monday, October 20, 2003 5:13 AM To: hansolofalcon(a)worldnet.att.net Subject: Forth Read your post on Forth . Where can i get on mailing list. I want to write a DTC Forth for i386 . It will be fast as it has 3 subroutine levels and lowest level is not Called , but the primatives Do have Returns at end ? ha ha They jmp directly to next primative . Stack must be preserved and restored to exit the prim' . ______________________________________________________________________ _ Dreaming of a Swiss Account? Get it here: http://freemail.swissinfo.org

1 0

V2 EPIA - IDE compat mode, RAM init, and early MTRR
by SONE Takeshi 21 Oct '03

21 Oct '03

Attached patch fixes IDE compatibility mode (so FILO works), and RAM initialization, so the DIMM on the second slot works. SPD is not used by this patch, we have to figure out how to type MA mapping by SPD (see the comment in the code). Maybe I will work on SPD-based RAM timing. earlymtrr.c should go to src/cpu/p6 so the XIP works. The change in src/cpu/p6/mtrr.c just reverse the change made by Eric for K8.. -- Takeshi

3 6

AMD8151
by Stefan Reinauer 21 Oct '03

21 Oct '03

Hi, I still don't get the 8151 to work properly on the solo board. i believe that the link setup looks like: Athlon64 | 8151 | 8111 since athlon64 has only one ht link. my config.lb defines: northbridge amd/amdk8 "mc0" southbridge amd/amd8151 "amd8151" link 0 end southbridge amd/amd8111 "amd8111" link [1|2] end end What is the right way of describing how the 8111 is connected in the config? And I only get hangs at: NB: Function 3 Misc Control.. IF I set amd8111 link to 0 I get a reboot plus hang at PCI: 03:00.2 [ffff/ffff] disabled amd8111_enable dev: PCI: 03:01.0 lpc_dev: PCI: 01:05.0 index: 9 reg: fe9f -> fce PCI: 03:01.0 [ffff/ffff] disabled PCI: 03:05.0 [14e4/1645] enabled Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.5.0-Fallback Mo Okt 20 11:35:43 CEST 2003 rebooting... I also noticed that not all elements in the capability linked list of the 8151 are HT capabilities. The first one on 8151 is an AGP capability element. Maybe this explains why a different ordered probing is needed, does LinuxBIOS correctly skip AGP capability blocks? Stefan -- ARCHITECTURE TEAM SUSE LINUX AG

2 4

cpu/p6/mtrr.c
by SONE Takeshi 21 Oct '03

21 Oct '03

Eric, Is the below change intended? EPIA has problem with current CVS (resets when setting var mtrr), and it worked again when I reversed this change. According to the Intel System Programming Manual for PIII, bits 36-63 are reserved, and apparently C3 doesn't like it to be set. black:~/src/freebios2/src/cpu/p6$ cvs diff -u -r1.4 -r1.5 mtrr.c Index: mtrr.c =================================================================== RCS file: /cvsroot/freebios/freebios2/src/cpu/p6/mtrr.c,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- mtrr.c 19 Jul 2003 04:28:21 -0000 1.4 +++ mtrr.c 11 Oct 2003 06:20:17 -0000 1.5 @@ -92,7 +92,7 @@ base.lo = basek << 10; if (sizek < 4*1024*1024) { - mask.hi = 0x0F; + mask.hi = 0x0FF; mask.lo = ~((sizek << 10) -1); } else { -- Takeshi

3 6

Fwd: via datasheets
by Greg Watson 20 Oct '03

20 Oct '03

Can anyone help this guy out? Greg >Status: U >To: jarrah(a)users.sourceforge.net >Subject: via datasheets >From: Yugesh <yugesh(a)users.sourceforge.net> >Cc: <yugesh(a)users.sourceforge.net> >Date: Mon, 20 Oct 2003 13:07:38 -0700 >X-Spam-Score: 0.0 (/) >X-Spam-Report: 0.0/5.0 > Spam Filtering performed by sourceforge.net. > See http://spamassassin.org/tag/ for more details. > Report problems to >https://sf.net/tracker/?func=add&group_id=1&atid=200001 > > >Hi, > > > >I don't know if you are able to help or not... I'm trying to get > >a hold of via datasheets to write some drivers. Specifically I > >need info on the VT8235 southbridge and vt82623 > >northbridge (CLE266 on an epia m10000). > > > >I noticed there was some via / epia code in your freebios > >code. > > > >Do you know where I can obtain information on the via > >chipsets ? > > > >I've tried requesting it from via with no response. > > > >Thanks.!

1 0

Re: EPIA version 2
by Russell Gower 20 Oct '03

20 Oct '03

----- Original Message ----- From: "ron minnich" <rminnich(a)lanl.gov> To: "Russell Gower" <russell(a)abc9986.demon.co.uk> Cc: "LinuxBIOS" <linuxbios(a)clustermatic.org> Sent: Sunday, October 12, 2003 4:42 PM Subject: Re: EPIA version 2 > On Sat, 11 Oct 2003, Russell Gower wrote: > > > I'm currently using the v1 tree for my EPIA based project, it looks like > > it's time for me to move over to the v2 tree. Is there any instructions on > > how to build linuxbios from the v2 tree? > > > > cd freebios2/targets > ./buildtarget via/epia > > that's a start to see how it is done. > > ron > > When I do that I get the following output. Traceback (innermost last): File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 2289, in ? if (not parse('board', fp.read())): File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1923, in parse return wrap_error_reporter(P, rule) File "/home/russell/linuxbios/freebios2/util/newconfig/yappsrt.py", line 162, in wrap_error_reporter try: return getattr(parser, rule)() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1850, in board loadoptions() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1004, in loadoptions if (not parse('options', fp.read())): File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1923, in parse return wrap_error_reporter(P, rule) File "/home/russell/linuxbios/freebios2/util/newconfig/yappsrt.py", line 162, in wrap_error_reporter try: return getattr(parser, rule)() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1916, in options define = self.define() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1910, in define defstmts = self.defstmts(ID) File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1876, in defstmts value = self.value() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1748, in value expr = self.expr() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1350, in expr logical = self.logical() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1365, in logical factor = self.factor() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1380, in factor term = self.term() File "/home/russell/linuxbios/freebios2/targets/epia/config.py", line 1406, in term return long(NUM, 10) TypeError: long requires exactly 1 argument; 2 given Russell.

3 2

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