coreboot

coreboot@coreboot.org

12 participants
39782 discussions

Re: filo on Tyan s2880
by YhLu 31 Oct '03

31 Oct '03

Sone, So if the user installed the Linux Distribution to HD in normal BIOS and after that he flash the ROM to LinuxBIOS with FIFO and the system call work without any problem. YH. -----邮件原件----- 发件人: SONE Takeshi [mailto:ts1@tsn.or.jp] 发送时间: 2003年10月30日 10:13 收件人: YhLu 抄送: Stefan Reinauer; linuxbios(a)clustermatic.org 主题: Re: filo on Tyan s2880 On Thu, Oct 30, 2003 at 09:49:49AM -0800, YhLu wrote: > What is the FIFO URL and the status? > Is it some kind payload for LinuxBIOS? FILO loads vmlinuz and ELF kernel from filesystem (like ext2) on the local IDE hard disk, CD-ROM, CompactFlash, or ROM. It's working well on my EPIA, and also reported to work with K8 based boards including Tyan's. See this for details: http://te.to/~ts1/filo/ My plan is to add support for configuration file, so the default kernel location and parameters will no longer be hard coded in the Flash, and Stephan told me maybe he can support this config file in the future releases of SuSE installation CDs. -- Takeshi

2 1

Re: running out of registers
by ebiederman＠lnxi.com 30 Oct '03

30 Oct '03

Stefan Reinauer <stepan(a)suse.de> writes: > Hi, > > I'm running out of registers with the Quartet code, I think it's in > spd_set_memclk(). That function has quite a lot of state variables, so > it seems hard to optimize registers away. The code goes fine without > the smbus_write_byte() but those are needed to select the correct > spdrom. Is it viable to add a couple of hooks to the code to trigger > selection of the hub channel? I guess doing this with every spd_read_byte > is quite some overkill and we might save some registers that way. That sounds like a reasonable idea. To confirm where you are running out of registers I would suggest commenting out the code in question to see if it compiles without it. Knowing that should help craft a solution. Depending on the nature of the problem and how we are running out of registers it might make sense to store a couple of values in a single variable. If you want to keep it from running forever before it gives up I suggest -fmax-allocation-passes=8 -fdebug-live-range-conflicts. The -fdebug-live-range-conflicts is not terribly interesting except it tells you how many passes romcc goes through before it gives up. The -fmax-allocation-passes=8 sets the limit on the number of register allocation passes romcc will use. The most I have seen it make and succeed in my regression tests is 6. And the default is 100. Eric

1 1

WD Caviar problem
by SONE Takeshi 30 Oct '03

30 Oct '03

I just found my old WD Caviar drive. It was in an unused PC. It's 1.2GB, WDC AC31200F. And the problem Steve reported is reproduced here. I'll see if I can fix this. -- Takeshi

4 12

help with filo
by Russell Gower 30 Oct '03

30 Oct '03

I'm trying to use filo to boot from a cdrom which is on hdb, it looks to me that using boot: hdb1 should do it but i'm getting Unsupported sector size 2352. Eltorito is enabled in the Config file. any suggestions? ICQ 4186920

2 2

filo on Tyan s2880
by Stefan Reinauer 30 Oct '03

30 Oct '03

Hi, I am using an etherboot payload that reads an elf image from the first sectors on the disk. This works fine, I put filo there so I can load a kernel from any filesystem. Unfortunately filo seems to find no IDE controller, it says IDE channel 0 not found. Etherboot and Linux can see the ide controller though (it's on bus 1) This happens with filo 0.4.1 Stefan -- Stefan Reinauer, SUSE LINUX AG Teamleader Architecture Development

2 2

Re: Support for Boser crusoe board?
by Richard Smith 29 Oct '03

29 Oct '03

Nick Jarmany wrote: > You should be aware that the Agilent (C&T) F69000 is end-of-life. Last shipments I believe are early next year. > Note its Asiliant not Agilent. http://www.asiliant.com Last time buy is Feburary 2004. The semi shop making the die is phasing out the process. I guess they were not moving enough of them to justify a re-spin onto a new smaller process. Of course they also may have not had the IP do it either. Asiliant is basically a bunch of ex-intel, who used to be C&T that when intel decided to shutdown C&T they bought the rights to the C&T dies and started selling them as Asiliant. It's possible that Intel only sold them the die masks and not the VHDL to generate them. And its a damn shame. Its caused us some heartache as we really didn't find a good replacemnet for them. We had to redesign our own SBC products with ATI M1 chips. ATI (via our Arrow vendor) has been _much_ more difficult to work with. -- Richard A. Smith rsmith(a)bitworks.com

2 1

RE: Support for Boser crusoe board?
by Nick Jarmany 29 Oct '03

29 Oct '03

You should be aware that the Agilent (C&T) F69000 is end-of-life. Last shipments I believe are early next year. Regards, Nick Jarmany > -----Original Message----- > From: linuxbios-admin(a)clustermatic.org > [mailto:linuxbios-admin@clustermatic.org]On Behalf Of Hubert Denkmair > Sent: 25 October 2003 20:15 > To: linuxbios(a)clustermatic.org > Subject: Support for Boser crusoe board? > > > Hello list, > > I have a very, VERY nice mini PC with Crusoe TM5400 / VIA VT82C686A > chipset here: > > http://www.boser.com.tw/products/sbc/hs1600.htm > > Linux works fine on it, now it would be cool if it was supported by > linuxbios. There seems to be support for the vt82c686 > (without 'A') in > the v1 source tree, but of course there is no direct support for the > Boser board. > > lspci says: > --- > 00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge > 00:00.1 RAM memory: Transmeta Corporation SDRAM controller > 00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad > 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo > Super South] > (rev 22) > 00:07.1 IDE interface: VIA Technologies, Inc. > VT82C586/B/686A/B PIPC Bus > Master IDE (rev 10) > 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10) > 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super > ACPI] (rev 30) > 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ (rev 10) > 00:09.0 VGA compatible controller: Chips and Technologies F69000 > HiQVideo (rev 64) > 00:0b.0 Multimedia audio controller: ESS Technology ES1969 Solo-1 > Audiodrive (rev 02) > --- > > Are there chances that this board will work with linuxbios? > If yes, what do I have to do to get it working? > > Hubert > --- > PS: lspci -v, don't know if it helps: > ---------------------------------------- > 00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge > Subsystem: Transmeta Corporation: Unknown device 0295 > Flags: bus master, medium devsel, latency 0 > Memory at e2000000 (32-bit, non-prefetchable) [size=1M] > > 00:00.1 RAM memory: Transmeta Corporation SDRAM controller > Subsystem: Transmeta Corporation: Unknown device 0295 > Flags: fast devsel > > 00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad > Subsystem: Transmeta Corporation: Unknown device 0295 > Flags: fast devsel > > 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo > Super South] > (rev 22) > Subsystem: VIA Technologies, Inc. VT82C686/A PCI to > ISA Bridge > Flags: bus master, stepping, medium devsel, latency 0 > > 00:07.1 IDE interface: VIA Technologies, Inc. > VT82C586/B/686A/B PIPC Bus > Master IDE (rev 10) (prog-if 8a [Master SecP PriP]) > Flags: bus master, medium devsel, latency 32 > I/O ports at c000 [size=16] > Capabilities: [c0] Power Management version 2 > > 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10) > (prog-if 00 > [UHCI]) > Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller > Flags: bus master, medium devsel, latency 32, IRQ 9 > I/O ports at c400 [size=32] > Capabilities: [80] Power Management version 2 > > 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super > ACPI] (rev 30) > Flags: medium devsel > Capabilities: [68] Power Management version 2 > > 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ (rev 10) > Subsystem: Realtek Semiconductor Co., Ltd. RT8139 > Flags: bus master, medium devsel, latency 32, IRQ 15 > I/O ports at cc00 [size=256] > Memory at e2100000 (32-bit, non-prefetchable) [size=256] > Capabilities: [50] Power Management version 2 > > 00:09.0 VGA compatible controller: Chips and Technologies F69000 > HiQVideo (rev 64) (prog-if 00 [VGA]) > Subsystem: Chips and Technologies F69000 HiQVideo > Flags: stepping, medium devsel, IRQ 12 > Memory at e0000000 (32-bit, non-prefetchable) [size=16M] > Expansion ROM at <unassigned> [disabled] [size=256K] > > 00:0b.0 Multimedia audio controller: ESS Technology ES1969 Solo-1 > Audiodrive (rev 02) > Subsystem: ESS Technology: Unknown device 8898 > Flags: bus master, medium devsel, latency 32, IRQ 5 > I/O ports at d000 [size=64] > I/O ports at d400 [size=16] > I/O ports at d800 [size=16] > I/O ports at dc00 [size=4] > I/O ports at e000 [size=4] > Capabilities: [c0] Power Management version 1 > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

1 0

speed of gunzip the kernel
by Bernd Mödeker 29 Oct '03

29 Oct '03

Hi list, our board needs for gunzipping the kernel 7s. I think this is not a good time. - board is geode SC1200 with 266MHz and CF-Card - size of linux.bin.gz is 1211422 bytes - linuxbios v1.0.0 has anyone some ideas why this unzipping is so slow? bernd

1 0

SC1200 and framebuffer under 2.4.22 without having vga-bios or VSA-bios is up
by Bernd Mödeker 29 Oct '03

29 Oct '03

Hi list, after several hours we did it. - Linuxbios-1.0.0 - Linux 2.4.22 with geode patches - framebuffer driver v2.77 If anyone is interested please mail me. Bernd

8 7

SST
by Xavier Pegenaute 28 Oct '03

28 Oct '03

Hi, now i want to try LinuxBios with an epia-m, any one know where i can find another flash memory by the case of an error while i'm trying? The code is: SST 39SF020A (70-4C-NH) Thanks a lot. Xavi.

4 3

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