Thread: [Etherboot-developers] Re: Etherboot 5.0.0 (production) released
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: Ken Y. <ke...@nl...> - 2001-04-25 15:41:09
|
And just so you know there's no rest for the wicked, here's a todo list. http://etherboot.sourceforge.net/todo.html If you think something ought to be on the list, discuss it on the developer list and I'll add it if it's technically worthy. That doesn't mean that I or anyone else for that matter will promise to do it. In fact, I'm hoping, against hope as always, that people other than the usual suspects (you know who you are) will take up the challenge. :-) Anyway, enough of this, I'm off to the beach tomorrow. |
|
From: Marty C. <md...@th...> - 2001-04-25 18:21:04
|
On 4/25/01 11:01 AM Ken Yap ke...@nl... wrote: >The Etherboot Project is pleased to announce the release of Etherboot 5.0.0, >the latest production version, available immediately from >http://sourceforge.net/projects/etherboot/. First, I'd like to thank Ken for all his good work on this release. He's good at thanking us other developers, so now it's our turn. Thanks, Ken! Great job!! Next, as is customary, I have updated http://rom-o-matic.net/ with the latest production release of Etherboot, version 5.0.0. http://rom-o-matic.net/ is generating about 1000 ROMs a week now, and if you visit the site, please click on the link to Etherboot so that the Sourceforge stats reflect the Etherboot activity as well. If rom-o-matic was hosted by Sourceforge, I think the project would be much higher in the stats. (even so, it is amazingly popular for a system utility). Anyway, it's great to get out a new release, and I hope we get to see lots of you at LinuxWorld Expo SF 2001 (http://www.linuxworldexpo.com/) where we will once again have an Etherboot booth. Now let's burn some ROMs and embed some code! :-) --- Try: http://rom-o-matic.net/ to make Etherboot images instantly. Name: Marty Connor US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA Voice: (617) 491-6935, Fax: (617) 491-7046 Email: md...@th... Web: http://www.thinguin.org/ |
|
From: Dirk v. S. <di...@go...> - 2001-04-25 20:43:44
|
> And just so you know there's no rest for the wicked, here's a todo list. > > http://etherboot.sourceforge.net/todo.html > > If you think something ought to be on the list, discuss it on the > developer list and I'll add it if it's technically worthy. That doesn't > mean that I or anyone else for that matter will promise to do it. In > fact, I'm hoping, against hope as always, that people other than the > usual suspects (you know who you are) will take up the challenge. :-) Moin, under the "BIOS" part was mentioned a tool for flashing biosses. There is such a thing in development: The /dev/bios project -> http://www.freiburg.linux.de/~stepan/bios/ for the linux kernel. With an older version I was able to flash the bios of some older socket7 intel vx mainboards. Unfortunately it does not compile for the 2.4.X kernel series at the moment. It does not work with relatively new chipsets and biosses greater than 256kByte. It would improve the efficiency of my work, if I had such a tool for linux, because I have no diskdrives installed on about 300 X terminals :-) I mailed the guy some weeks ago, but he is working on porting SuSE-linux to axp (?) platform. Maybe if some more people asking him for this tool he gives some more efforts to this project :-) So long, Dirk |
|
From: <ebi...@ln...> - 2001-04-25 20:46:20
|
Dirk von Suchodoletz <di...@go...> writes: > > And just so you know there's no rest for the wicked, here's a todo list. > > > > http://etherboot.sourceforge.net/todo.html > > > > If you think something ought to be on the list, discuss it on the > > developer list and I'll add it if it's technically worthy. That doesn't > > mean that I or anyone else for that matter will promise to do it. In > > fact, I'm hoping, against hope as always, that people other than the > > usual suspects (you know who you are) will take up the challenge. :-) > > Moin, > under the "BIOS" part was mentioned a tool for flashing biosses. > There is such a thing in development: The /dev/bios project -> > http://www.freiburg.linux.de/~stepan/bios/ > for the linux kernel. With an older version I was able to flash the bios > of some older socket7 intel vx mainboards. Unfortunately it does not > compile for the 2.4.X kernel series at the moment. It does not work with > relatively new chipsets and biosses greater than 256kByte. It would > improve the efficiency of my work, if I had such a tool for linux, because > I have no diskdrives installed on about 300 X terminals :-) > > I mailed the guy some weeks ago, but he is working on porting SuSE-linux > to axp (?) platform. Maybe if some more people asking him for this tool he > gives some more efforts to this project :-) Actually this work just needs to get folded into the current mtd drivers in the 2.4 kernel. The infrastructure is nicer and they are being actively developed and maintained. Eric |
|
From: Dirk v. S. <di...@go...> - 2001-04-25 20:59:25
|
> > I mailed the guy some weeks ago, but he is working on porting SuSE-linux > > to axp (?) platform. Maybe if some more people asking him for this tool he > > gives some more efforts to this project :-) > > Actually this work just needs to get folded into the current mtd drivers > in the 2.4 kernel. The infrastructure is nicer and they are being actively > developed and maintained. Dont know much of kernel programming and these MTD :-( As I heard the BIOS must be accessed via the mainboard chipset. Do this type of flash match into the concepts of the MTD? It would be great to have a more general driver for steady development, than a single kernel module patch... Ciao, Dirk |
|
From: <ebi...@ln...> - 2001-04-25 21:11:28
|
Dirk von Suchodoletz <di...@go...> writes: > > > I mailed the guy some weeks ago, but he is working on porting SuSE-linux > > > to axp (?) platform. Maybe if some more people asking him for this tool he > > > gives some more efforts to this project :-) > > > > Actually this work just needs to get folded into the current mtd drivers > > in the 2.4 kernel. The infrastructure is nicer and they are being actively > > developed and maintained. > > Dont know much of kernel programming and these MTD :-( Quite a bit. And once you have the docs to the motherboards, and chipsets, and flash memories everything is straightforward and simple. Getting the docs for motherboards tends to be the tricky part. But I haven't really looked into the general case. Just one or two specific cases. > As I heard the BIOS must be accessed via the mainboard chipset. You need to map the BIOS into your address space, and about half the time you need to enable writes to the BIOS. > Do this type of flash match into the concepts of the MTD? Yes. You just need a per-chipsest or per-motherboard mapping driver to enable the writes, and allow access to it. > It would be great to have a more general driver for steady development, > than a single kernel module patch... The basic mtd stuff works well. Eric |