coreboot June 2004

coreboot@coreboot.org

43 participants
102 discussions

答复: [COMMIT] romcc 0.63 and some fixes...
by YhLu 07 Jun '04

07 Jun '04

Just sent out the core. -----邮件原件----- 发件人: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] 发送时间: 2004年6月3日 17:23 收件人: YhLu 抄送: LinuxBIOS 主题: Re: [COMMIT] romcc 0.63 and some fixes... YhLu <YhLu(a)tyan.com> writes: > Eric, > > I'm not familiar the gdb, and if you like I can send the auto.E to you. That would be good thanks. I guess slightly simpler would be to do: Which will ensure core file generation is not turned off. Then you can do. ulimit -c unlimited make find . -name 'core*' -print find . -name 'romcc' -print And send me (off list) the file named core file and the file named romcc, that the above find commands found. This feels like gcc miscompiled romcc or something like that. "ulimit -c unlimited" ensures core generation is enabled. "make" does the build that fails "find . -name 'core*' -print" locates core file generated by the sigsegv "find . -name 'romcc' -print" locates the romcc binary you were running. If it is a compilation error I really need to see what the binaries look like. If it a bug in romcc I should be able to feed in your auto.E and reproduce this. Some very strange things are going on and I don't know how to call it. Running dmesg and seeing if the oom killer kicked in would also be interesting. romcc tends to be a bit of a memory hog. Not so much that it has been unusable but I am grasping at straws. It looks like my next step in instrumenting romcc is to start catching signals like sigsegv so I can exit moderately gracefully when they occur. My coworkers have been using the romcc with no ill effects so I am truly mystified, as to what is going wrong. Thanks, Eric P.S. Brain storming on naming conventions, I think the sanest thing to do is to indicate a function is not inline by appending an underscore to it's name. So we will have print_debug(str) and pring_debug_(str).... Unless there are any objections.

2 2

Re: Difference between Linxubios native's Elfboot and Linuxbios native's Filo
by ebiederman＠lnxi.com 07 Jun '04

07 Jun '04

Mathieu Deschamps <mdeschamps(a)mangrove-systems.com> writes: > Hello, > > Since i have mostly 'directly choose' Filo, i haven't had > much time asking for the difference between Linuxbios native's Elfboot > and Linuxbios native's filo. I know you did made some work around > theses... The native ``filo'' is scheduled for deletion, it touches hardwaremain which it should not. As implemented it is a maintenance nightmare and an implementation of policy and I refuse to support it, in the core of LinuxBIOS. Until just a little while ago I thought it was much less intrusive so was not forcing the issue. > (i have read the doc of Sone Takeshi and i have the features of filo.) > > Could you explain me what differences there are and/or whether > this one best suited for DoC or CF or other types i'am ignoring ? > Please also let me know what type of filesys elfboot boots, and other > thing about support ELF boot is a minimal loader just good enough to load something real out off some device. ELF boot just grabs an ELF image at the offset in a device it is pointed at. The image can be sparse so it can exist with partition tables and filesystems. The trivial solution is to put a partition right after partition table for the ELF image. More interesting forms of coexistance are possible by noone has implemented more than a proof of concept. If you want to use filo which understand filesystems and partitions get the real one. It has been developing faster and it appears to have more features. Eric

4 8

http://www.linuxbios.org/developer/download/
by Ken Fuchs 07 Jun '04

07 Jun '04

Sorry, there doesn't appear to be a webmaster e-mail address for linuxbios.org, so I'm sending this web site update request to the LinuxBIOS mailing list. Please correct the cvs commands' hostname. It should be cvs.sourceforge.net, not cvs.freebios.sourceforge.net. It would also be helpful to suggest that the environment variable CVS_RSH be set to ssh prior to using any cvs command (example for bash below): $ export CVS_RSH=ssh Sincerely, Ken Fuchs <kfuchs(a)winternet.com>

1 0

CPL and GPL
by YhLu 05 Jun '04

05 Jun '04

It seems one EFI implementation in 32 bit. What's the major difference between CPL and GPL? Regards YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年6月1日 17:31 收件人: Bari Ari 抄送: Steve Gehlbach; Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: ACPI DSDT On Tue, 1 Jun 2004, Bari Ari wrote: > Here's the official Intel statement: > > http://www.intel.com/pressroom/archive/releases/20040601corp_a.htm gee, no mention of linuxbios :-) ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

intel 875P support
by YhLu 04 Jun '04

04 Jun '04

Who is working on intel 875P northbridge? Regards YH

1 0

briQ status
by Greg Watson 04 Jun '04

04 Jun '04

For those interested in PPC boards, I just managed to get the briQ talking over serial console. (More on the board at http://www.totalimpact.com/products/the_briq/the_briq.html). Output below. Hopefully we'll demo this board running Clustermatic at the USENIX BOF. Greg Board initialized... LinuxBIOS-1.1.6 Fri Jun 4 16:13:35 MDT 2004 rebooting... Finding PCI configuration type. Enumerating static devices... Enumerating buses... PCI: pci_scan_bus for bus 0 PCI: 00:00.0 [1014/0105] enabled PCI: 00:06.0 [10ad/0565] ops PCI: 00:06.0 [10ad/0565] enabled PCI: 00:06.1 [10ad/0105] ops PCI: 00:06.1 [10ad/0105] enabled PCI: 00:07.0 [1022/2000] enabled PCI: pci_scan_bus returning with max=00 done Allocating resources... ASSIGN RESOURCES, bus 0 PCI: 00:06.1 10 <- [0x00001040 - 0x00001047] io PCI: 00:06.1 14 <- [0x00001050 - 0x00001053] io PCI: 00:06.1 18 <- [0x00001048 - 0x0000104f] io PCI: 00:06.1 1c <- [0x00001054 - 0x00001057] io PCI: 00:06.1 20 <- [0x00001020 - 0x0000102f] io PCI: 00:06.1 24 <- [0x00001030 - 0x0000103f] io PCI: 00:07.0 10 <- [0x00001000 - 0x0000101f] io PCI: 00:07.0 14 <- [0xfebfffe0 - 0xfebfffff] mem ASSIGNED RESOURCES, bus 0 done. Enabling resourcess... PCI: 00:00.0 cmd <- 147 PCI: 00:06.0 cmd <- 147 PCI: 00:06.1 cmd <- 145 PCI: 00:07.0 cmd <- 143 done. Initializing devices... PCI: 00:06.0 init Configure W83C553F ISA Bridge (Function 0) W83C553F configuration complete PCI: 00:06.1 init Configure W83C553F IDE (Function 1) ide bus offset = 0x1f1 IDE configuration complete Devices initialized totalram: 1024M Initializing CPU #0 PowerPC 7400 CPU, version 2.9 CPU #0 Initialized Wrote linuxbios table at: 00000010 - 00000174 checksum 9bf0 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3 Trying polled ide Waiting for ide disks to spin up This is a hard coded delay and longer than necessary. .. found PCI IDE controller 10ad:0105 prog_if=0x8f primary channel: native PCI mode

1 0

Tool Versions
by Jay Miller 04 Jun '04

04 Jun '04

I'm still having trouble building etherboot .zelf images. It appears that the file size in the elf header is corrupt, and someone here suggested that I may have a buggy version of Perl. Here are the versions in my toolchain: Red Hat 9.0 box with: Gcc 3.3.3 Python 2.2.2 Perl 5.8.4 (latest & greatest) Binutils-2.15 Any thoughts? Thanks, Jay Miller Actuality Systems, Inc. jmiller(a)acutality-systems.com

1 0

Looking for Laptop Candidates for LinuxBIOS Port
by Bari Ari 03 Jun '04

03 Jun '04

We are in search of good candidates for laptops for a LinuxBIOS Port. These will be the easiest to port: Intel laptops with Intel integrated graphics, not ATI or nVidia graphics Intel Chipsets (TBA) i915 http://www.tbreak.com/reviews/article.php?id=305 These should be out in the next month or so. 855GM http://developer.intel.com/design/chipsets/mobile/855gm.htm?iid=dev_chips85… 852GME http://developer.intel.com/design/chipsets/mobile/855GME.htm?iid=dev_chips8… 852GM http://developer.intel.com/design/chipsets/mobile/852gm.htm 852GMV http://developer.intel.com/design/chipsets/mobile/852gmv.htm Along with any of these Renesas keyboard/system controllers: http://www.renesas.com/eng/products/mpumcu/16bit/h8s/2100/ Everyone please crack open those lids and check your lspci's. Go down in LinuxBIOS history as the one that came up with the winner! -Bari

1 0

Re: [COMMIT] romcc 0.63 and some fixes...
by YhLu 03 Jun '04

03 Jun '04

I will add RAM to test again. Regards YH

1 0

Re: [COMMIT] romcc 0.63 and some fixes...
by ebiederman＠lnxi.com 03 Jun '04

03 Jun '04

YhLu <YhLu(a)tyan.com> writes: > Eric, > > I'm not familiar the gdb, and if you like I can send the auto.E to you. That would be good thanks. I guess slightly simpler would be to do: Which will ensure core file generation is not turned off. Then you can do. ulimit -c unlimited make find . -name 'core*' -print find . -name 'romcc' -print And send me (off list) the file named core file and the file named romcc, that the above find commands found. This feels like gcc miscompiled romcc or something like that. "ulimit -c unlimited" ensures core generation is enabled. "make" does the build that fails "find . -name 'core*' -print" locates core file generated by the sigsegv "find . -name 'romcc' -print" locates the romcc binary you were running. If it is a compilation error I really need to see what the binaries look like. If it a bug in romcc I should be able to feed in your auto.E and reproduce this. Some very strange things are going on and I don't know how to call it. Running dmesg and seeing if the oom killer kicked in would also be interesting. romcc tends to be a bit of a memory hog. Not so much that it has been unusable but I am grasping at straws. It looks like my next step in instrumenting romcc is to start catching signals like sigsegv so I can exit moderately gracefully when they occur. My coworkers have been using the romcc with no ill effects so I am truly mystified, as to what is going wrong. Thanks, Eric P.S. Brain storming on naming conventions, I think the sanest thing to do is to indicate a function is not inline by appending an underscore to it's name. So we will have print_debug(str) and pring_debug_(str).... Unless there are any objections.

1 0

← Newer
1
...
4
5
6
7
8
9
10
11
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 June 2004