April 2004 - coreboot - mail.coreboot.org

Re: flash_rom start and size
by YhLu April 21, 2004

April 21, 2004

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 April 21, 2004

April 21, 2004

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

FILO --> zelf format to reduce size to 32k below.
by YhLu April 21, 2004

April 21, 2004

Eric, Can you add something in filo Makefile and make it produce zelf format? If the size to be 32k below, for fallback boot the payload could be FILO+Etherboot --> [384k, 416k](FILO) + [416k, 448k) (Etherboot) , instead of putting the Etherboot in the [0,64k) of ROM, and FILO in the [384k, 448k). Regards YH

1 0

flash_rom start and size
by YhLu April 21, 2004

April 21, 2004

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. Regards YH

2 1

RE: flash_n_burn rom utils, /dev/bios ... resquest
by John Usher (Maptek) April 21, 2004

April 21, 2004

For what it's worth (and so far it only works on a win* machine, we use the following cheap programmer with our ST M29F040B parts. Works a treat, but programming through the lpt port is not the fasted. The fact that only windows is supported is also a bit of a bummer. http://www.jedmicro.com.au/PROM.htm j -----Original Message----- From: ron minnich [mailto:rminnich@lanl.gov] Sent: Wednesday, 21 April 2004 8:20 AM To: Ian Zimmerman Cc: linuxbios(a)clustermatic.org Subject: Re: flash_n_burn rom utils, /dev/bios ... resquest On 20 Apr 2004, Ian Zimmerman wrote: > Same here. > > I feel that the reliance on hotplugging flash chips has limited > linuxbios audience to hard-core metal hackers. but what else can you do? Can you afford a flash burner? The set of people who can afford this is smaller than the set of people who can hot plug. I had not realized however that hot plug is such a big issue, so suggestions for alternatives that are affordable would be great Thanks! ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

7 10

EPIA-M IRQ cvs update
by Dave Ashley April 20, 2004

April 20, 2004

>committed, cvs update and try again, and thanks for your patience. I tried this but none of your recent cvs commits are visible (the earlysetup.inc or the mainboard.c change). Remember I'm still just using the pond-scum cvs server: cvs -z3 -d:pserver:anonymous@cvs.freebios.sourceforge.net:/cvsroot/freebios co freebios -Dave

4 4

RE: epia-m latest cvs works
by M. Renee Hopkins April 20, 2004

April 20, 2004

I just built fresh LB from CVS for EPIA-M ME-600. Seems a lot of progress has been made. Payload included VGA bios and FILO. Seems like most all components detected. I'm going to test MPEG, X11, mouse and will report soon. Previously, MPEG2 used too much CPU and was jerky, AGP seemed slow, mouse was very slow. Thanks LB Team! 00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (re v 80) 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/ VT8235 PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Aud io Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] i ntegrated CastleRock graphics (rev 03) _________________________________________________________________ >From must-see cities to the best beaches, plan a getaway with the Spring Travel Guide! http://special.msn.com/local/springtravel.armx

1 0

epia-m latest cvs works
by Dave Ashley April 20, 2004

April 20, 2004

I cvs updated and the latest changes were there (earlysetup.inc and the mainboard.c). I built the rom with this script: # Modify the example.config to point to the right payloads for vgabios.bin # and the etherboot payload cd /ram/build rm -rf obj python /ram/freebios/util/config/NLBConfig.py example.config /ram/freebios/ make -C obj NOTE: I had /ram/freebios as the cvs checked out tree. Here is the diff on the example.config from the tree and the one I used: 5d4 < target /opt/cwlinux/buildrom/epia-m 28c27 < target /ram/freebios/obj --- > target /ram/build/obj 48c47 < payload /opt/cwlinux/etherboot/src/bin32/via-rhine.ebi --- > #payload /opt/cwlinux/etherboot/src/bin32/via-rhine.ebi Which is pretty simple, just picking my payload and vgabios.bin. My vgabios.bin is just extracted from the c000:0000 memory after having boot up from the stock bios, same as everyone else's. My payload is based on etherboot 5.0.10 but other versions of etherboot are fine too. Anyway this tree builds fine for my needs. It also appears the temperature monitoring functions of the VT1211 are also working correctly. One of the tweaks I do in my version now is switch the ttyS0 and ttyS1 so ttyS0 ends up being the inside one. Now that I think about it there is an obscure bit I had to set to enable that internal port, but I've posted about this in this mailing list. I think I enable the parallel port also. I don't enable the IDE controller(s) but those appear to be on now but I'm not sure. -Dave

2 1

EPIA-M IRQ [FIXED]
by Dave Ashley April 19, 2004

April 19, 2004

>once more, shall we diff CVS and your tree? this is something simple, I >know, just not sure what. I fixed it by modifying this file freebios/src/mainboard/via/epia-m/mainboard.c Inside final_southbridge_fixup add this at the bottom of the function: pci_routing_fixup(); I've booted off this latest version with my payload + my vgabios.bin and have SVGA output working, mpeg-2 video playback working, audio out working, networking up, the pci-card we have in the epia-m functions fully. I think with this change it is good to go for V2. This doesn't require any changes in the linux ebi file I load with the etherboot payload. -Dave

2 1

epia-m IRQ issue
by Dave Ashley April 19, 2004

April 19, 2004

I've stuck in my own earlysetup.inc file and it works ok. My payload and my vgabios.bin seem to function but I'm dying inside linux because none of the IRQ's are assigned. I put in some debug code and the IRQ numbers in the pci configuration space don't seem to be getting set. For example the ethernet controller has IRQ 0 for its setting. There is no change to linux required to get this to work right, something is broken in linuxbios that was working before. PCI routing tables--I don't even really understand what these are, don't know if they apply here. Linux is scanning the pci config space to get the bios assigned irq's and they are probably all 0. -Dave

2 1