coreboot

coreboot@coreboot.org

10 participants
39711 discussions

On which mainboards does LinuxBIOS function best?
by Ken Fuchs 23 Apr '04

23 Apr '04

The status web page has only three values for each mainboard: unsupported, unstable (not verified stable) and stable. There doesn't seem to be an easy way to tell whether one mainboard works better than another. How does one know whether LinuxBIOS on a particular mainboard supports multiuser X for example? How does one determine which DoC models are supported, i.e. M2800, M2802, M2808, M2811, M3331, etc. for a particular mainboard BIOS socket? I assume the mainboards with 512KB (2Mb) BIOS should contain a full compressed LinuxBIOS kernel. Would 1MB or more be recommended? I'm looking for an inexpensive 1P AMD mainboard on which I can install LinuxBIOS with relative ease and gain maximum LinuxBIOS functionality from it. I would also like to follow one of the HOWTOs or create a new HOWTO for such a mainboard. Any mainboard suggestions? Would a DoC be required? Sincerely, Ken Fuchs <kfuchs(a)winternet.com>

1 0

答复: ATI rage xl.init
by YhLu 22 Apr '04

22 Apr '04

Ron, I have enabled the ati rage xl frame buffer in LinuxBIOS, also moved the btext.c to the LinuxBIOS. So I can get output on CRT in LinuxBIOS after the ati device init. I'm going to add one console besides console8250.c and vgaconsole.c. Please suggest the console name for that: 1. fbconsole.c 2. or btextconsole.c to honor the btext.c author The btext.c is in the linux/arch/ppc/kernel/btext.c Regards YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月14日 15:01 收件人: Brian Maly 抄送: linuxbios(a)clustermatic.org 主题: Re: ATI rage xl.init Ollie knows better than me but I'm guesssing there are still some registers not set right in linuxbios. Note that to date for our nvidia stuff we've had to set these registers by hand in a shell script. VGA is still not quite right, but we're trying to get it. ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

3 2

答复: flash_rom start and size
by YhLu 22 Apr '04

22 Apr '04

For example, 1. I only want to let end user to flash normal part [0-384k), and don't let him touch fallback part [384k, 512k). 2. or I only want to update the payload image in the beginning, [0,64k). Regards Yinghai Lu -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月21日 9:09 收件人: YhLu 抄送: LinuxBIOS 主题: Re: flash_rom start and size On Tue, 2004-04-20 at 20:06, YhLu wrote: > Ollie or David, > > Can you modify the flash_rom to take start and size command line? > > I mean > > Flash_rom -start=0k -size=384k xxxx.rom > > And xxxx.rom only to be 384k. > Why do you want to do this ? You should prepare the image the same size as your flash chip. There are techinical difficulty doing this. Most flash parts are block/sector erase and byte program. There is no general way to start from an abitrary address to any size. Ollie > Regards > > YH >

3 2

descriptive subject ;)
by Mathieu Deschamps 22 Apr '04

22 Apr '04

* Mathieu Deschamps <mdeschamps(a)mangrove-systems.com> [040421 09:48]: > ps final 'peak' : IMO, putting [linuxbios] before titles is a *bad* > idea : on a linuxbios maillist, the only root topic is linuxbios > obviously so no need to repeat it in title ... >I disagree. It's a good thing to detect quickly and easily whether >a mail is private or coming in via the list. > >Stefan Simple to notice this : all the message in which I'am CC i got them twice in my mail box. quick & simple. Otherwise I got them just once (coming just from via the list). Honestly i found this sole system enough, what is more some message I believed to be not interessing to me (after reading) appear to be relevant later on : maybe it's because i'am a rookie :) mathieu

1 0

descriptive subjects ;)
by Stefan Reinauer 22 Apr '04

22 Apr '04

1 0

EPIA (NOT EPIA-M) VGA
by ron minnich 22 Apr '04

22 Apr '04

Sorry, I've lost track. Has anyone here tested EPIA VGA? Does it work? I've just gotten a request for an EPIA with VGA running Filo. ron

1 0

答复: ATI rage xl.init
by YhLu 21 Apr '04

21 Apr '04

I use stefan Linuxbios snapshots to produce diff. If there still problem, I would send you my tree tar ball. Regards YH -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月21日 14:47 收件人: YhLu 抄送: ron minnich; Stefan Reinauer; LinuxBIOS 主题: Re: ATI rage xl.init On Tue, 2004-04-20 at 19:38, YhLu wrote: > Ron, > > Please commit ati rage xl support. > > 1. ati rage xl support > 2. add btext_console to use rage xl fb. > 3. enable pnp init calling > 4. superio Winbond: real enable/disable device. > 5. superio Winbond: enable HW > 6. Tyan S2850 support update > 7. Tyan S2875 support added. > 8. Move some PCI master enable driver to /driver dir. > > Stefan, > > Please test the filo too, I add the btext_console into it. > On vocation? Why using stepan(a)openbios.org ? > > there are some conflicts between your tree and the current CVS. Could you do cvs update and send me the patch again ? Ollie

1 0

答复: flash_rom start and size
by YhLu 21 Apr '04

21 Apr '04

It could only process 64k block. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月21日 10:29 收件人: YhLu 抄送: Li-Ta Lo; LinuxBIOS 主题: Re: flash_rom start and size for the Alphas long ago I modified flash_rom as follows: flash_rom e <start block #> <length in blocks> Erase the blocks flash_rom r <start block #> <length in blocks> read the blocks flash_rom p <file name> <start block #> program with file name starting at start block #. Program up to the limit of the file size or the flash size, whichever is small. This was for partial programming. flash_rom s <start block #> <lenght in blocks> program using stdin as the data, starting at start block # and for length blocks OR eof on stdin, whichever was smaller. This was pretty handy for the DS10, which had 2 MB of flash in 64KB blocks, and had areas of flash we could not rewrite. maybe we need this for the general case? ron

2 1

Re: flash_rom start and size
by YhLu 21 Apr '04

21 Apr '04

In the PMC pm49fl004, You got eight 64K size blocks. You can erase the individual block and write that block only. Regards YH -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月21日 9:49 收件人: YhLu 抄送: LinuxBIOS 主题: Re: 答复: flash_rom start and size On Wed, 2004-04-21 at 10:40, YhLu wrote: > For example, > 1. I only want to let end user to flash normal part [0-384k), and don't let > him touch fallback part [384k, 512k). there is no way you can really lock the flash. > 2. or I only want to update the payload image in the beginning, [0,64k). > you need some kind of flash translation layer to accomplish this. You need to back up some part of the erase block you want reserve , erase the block and write with updated and reserved data. You probably need MTD. Ollie > Regards > > Yinghai Lu > -----邮件原件----- > 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] > 发送时间: 2004年4月21日 9:09 > 收件人: YhLu > 抄送: LinuxBIOS > 主题: Re: flash_rom start and size > > On Tue, 2004-04-20 at 20:06, YhLu wrote: > > Ollie or David, > > > > Can you modify the flash_rom to take start and size command line? > > > > I mean > > > > Flash_rom -start=0k -size=384k xxxx.rom > > > > And xxxx.rom only to be 384k. > > > > Why do you want to do this ? You should prepare the image > the same size as your flash chip. > > There are techinical difficulty doing this. Most flash > parts are block/sector erase and byte program. There is > no general way to start from an abitrary address to any > size. > > Ollie > > > Regards > > > > YH > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

3 2

flash_n_burn rom utils, /dev/bios ... resquest
by Mathieu Deschamps 21 Apr '04

21 Apr '04

Hello, I was wondering in what measure it would be possible to read/write a bios via a LPT port. If i am not mistaking, every flashing facility solution reads/writes a onboard bios chip. I know this could sound very strange to you. Also, I know how difficult it is to handle request that steps aside of what the system is meant to do. But I don't feel confident with bios hot plugging... I've read this is a sensible operation and well ... Mainly i couldn't afford to "break" my unique build machine bios ! I'd rather like to make a backup copy of my bios in another chip and then to cold plug this copy to work with Linuxbios. Has anyone felt this worry . How come could I resolve this ? thanks in advance mathieu

7 10

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