etherboot-developers Mailing List for Etherboot (Page 179)
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-developers — Discussion of developer issues
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(3) |
Oct
(10) |
Nov
(47) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(41) |
Feb
(107) |
Mar
(76) |
Apr
(103) |
May
(66) |
Jun
(72) |
Jul
(27) |
Aug
(31) |
Sep
(33) |
Oct
(18) |
Nov
(33) |
Dec
(67) |
| 2002 |
Jan
(25) |
Feb
(62) |
Mar
(79) |
Apr
(74) |
May
(67) |
Jun
(104) |
Jul
(155) |
Aug
(234) |
Sep
(87) |
Oct
(93) |
Nov
(54) |
Dec
(114) |
| 2003 |
Jan
(146) |
Feb
(104) |
Mar
(117) |
Apr
(189) |
May
(96) |
Jun
(40) |
Jul
(133) |
Aug
(136) |
Sep
(113) |
Oct
(142) |
Nov
(99) |
Dec
(185) |
| 2004 |
Jan
(233) |
Feb
(151) |
Mar
(109) |
Apr
(96) |
May
(200) |
Jun
(175) |
Jul
(162) |
Aug
(118) |
Sep
(107) |
Oct
(77) |
Nov
(121) |
Dec
(114) |
| 2005 |
Jan
(201) |
Feb
(271) |
Mar
(113) |
Apr
(119) |
May
(69) |
Jun
(46) |
Jul
(21) |
Aug
(37) |
Sep
(13) |
Oct
(4) |
Nov
(19) |
Dec
(46) |
| 2006 |
Jan
(10) |
Feb
(18) |
Mar
(85) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(10) |
Jul
(20) |
Aug
(9) |
Sep
(11) |
Oct
(4) |
Nov
(1) |
Dec
(40) |
| 2008 |
Jan
(19) |
Feb
(8) |
Mar
(37) |
Apr
(28) |
May
(38) |
Jun
(63) |
Jul
(31) |
Aug
(22) |
Sep
(37) |
Oct
(38) |
Nov
(49) |
Dec
(24) |
| 2009 |
Jan
(48) |
Feb
(51) |
Mar
(80) |
Apr
(55) |
May
(34) |
Jun
(57) |
Jul
(20) |
Aug
(83) |
Sep
(17) |
Oct
(81) |
Nov
(53) |
Dec
(40) |
| 2010 |
Jan
(55) |
Feb
(28) |
Mar
(36) |
Apr
(7) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
(10) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Paolo S. <al...@io...> - 2003-09-18 07:52:34
|
Hi! > >I'me playing with the autoprobing etherboot.zdsk image... > >My target is to build a universal thinclient boot-disk... > >Some suggestion to make it more usable: > > An explanation: Originally each image only contained one driver and they > were intended for ROMs so it was assumed that if it didn't work you had > the wrong ROM, so no consideration was given to what to do on failure. > Of course now that the drivers are on floppy and can be combined, they > don't cooperate well. Yes, I perfectly comprehend why it have this behaviour! We are trying to do a thing it simply wasn't born for... but I'm sure that with little effort we can have it to work perfectly even in this context! > >- some ISA driver try probing infinite times, until the user press ESC > >to probe next driver; > >it would be nicer to put a limit on probing, so after a while it will > >automatically probe next driver > > You can help us by compiling and sending us a table that lists each > driver and how it behaves less than satisfactorily. Ok, if needed I can do it.... but the simplest and fastest way is building the etherboot.zdsk image, make the floppy, and try it on a PC without network card (so it will probe everything....): the main target is having no driver probing infinite times the same network card (so no ESC will be required...); the second target is having coherent and limited output from each driver probing... > >- when probing, some driver fill the screen with "."s, some other with > >"(probe failed)"s, and so on... more coherence will be appreciated! > > I think the probe failed message is only in the 3c509 and should be > suppressed. I can't think offhand where the dots come from since no > packets are sent out at that point yet. If I remember well, after pressing "ESC" on the 3c509 driver, I can't see what is written on the screen 'cause it is filled with dots! Haven't understood the reason... > >Thinking that a lot of driver could potentially do the probing, to avoid > >filling the screen, the best solution could be something like: > > > >[3c5x9] Probing.......... > >[NE] Probing... > >[SMC9000] Probing........................ > >[3c529] Probing.......found! > > > >- driver probing order: some isa driver doesn't seem to require tons of > >probe, some other requir it.... driver probing order should be decided > >with attention, because these latter drivers should be probed after the > >former > > The order of probing is the order of linking. If you can devise a means > of specifying the link order... Is it influenced by the order of the object files passed to the compiler? > >- lance driver: can it works in the etherboot.zdsk? > >I removed it from genrules.pl, otherwise I couldn't compile... > > No, not in relocated mode and without relocation you won't be able to > fit all the drivers in. Essentially lance should not be used in 5.2, > unless you use it by itself and without relocation. Use pcnet32 for the > PCI Lance NICs. No problem... the big problem was WHERE to put my hand to prevent this file to be included in etherboot.zdsk; at the end I changed genrules.pl, but I'm not really sure it is the right place... > >- in etherboot.zdsk it seems to me there are image not really useful > >(like the disk driver or the skeleton...); they could be eliminated from > >the etherboot build script > > Send us a patch. > > >- etherboot-pci.zdsk seems to try anyway to probe ISA card... not nice > > Does it? Maybe you can have a look and see why? > > Thanks for the suggestions. If you can provide more detailed information > or even patches, that will be even more helpful. I'm not a developer, so I can only provide more informations... ;o( I think we should provide a simple way to build custom "50 driver in a single image" image: ie, providing a file with the driver list somone want to include... This file could be auto generated during the build process, and the user can comment/uncomment the drivers he want to include in the final image... Ok... this is all! Paolo |
|
From: <ke...@et...> - 2003-09-18 02:07:52
|
>I'me playing with the autoprobing etherboot.zdsk image... > >My target is to build a universal thinclient boot-disk... > >Some suggestion to make it more usable: An explanation: Originally each image only contained one driver and they were intended for ROMs so it was assumed that if it didn't work you had the wrong ROM, so no consideration was given to what to do on failure. Of course now that the drivers are on floppy and can be combined, they don't cooperate well. >- some ISA driver try probing infinite times, until the user press ESC >to probe next driver; >it would be nicer to put a limit on probing, so after a while it will >automatically probe next driver You can help us by compiling and sending us a table that lists each driver and how it behaves less than satisfactorily. >- when probing, some driver fill the screen with "."s, some other with >"(probe failed)"s, and so on... more coherence will be appreciated! I think the probe failed message is only in the 3c509 and should be suppressed. I can't think offhand where the dots come from since no packets are sent out at that point yet. >Thinking that a lot of driver could potentially do the probing, to avoid >filling the screen, the best solution could be something like: > >[3c5x9] Probing.......... >[NE] Probing... >[SMC9000] Probing........................ >[3c529] Probing.......found! > >- driver probing order: some isa driver doesn't seem to require tons of >probe, some other requir it.... driver probing order should be decided >with attention, because these latter drivers should be probed after the >former The order of probing is the order of linking. If you can devise a means of specifying the link order... >- lance driver: can it works in the etherboot.zdsk? >I removed it from genrules.pl, otherwise I couldn't compile... No, not in relocated mode and without relocation you won't be able to fit all the drivers in. Essentially lance should not be used in 5.2, unless you use it by itself and without relocation. Use pcnet32 for the PCI Lance NICs. >At the beginning, when it lists all present drivers, plesase separe them >with a space! Tastes differ. The current packing is perfectly readable to me. >- in etherboot.zdsk it seems to me there are image not really useful >(like the disk driver or the skeleton...); they could be eliminated from >the etherboot build script Send us a patch. >- etherboot-pci.zdsk seems to try anyway to probe ISA card... not nice Does it? Maybe you can have a look and see why? Thanks for the suggestions. If you can provide more detailed information or even patches, that will be even more helpful. |
|
From: Paolo S. <al...@io...> - 2003-09-17 16:52:50
|
Hi! I'me playing with the autoprobing etherboot.zdsk image... My target is to build a universal thinclient boot-disk... Some suggestion to make it more usable: - some ISA driver try probing infinite times, until the user press ESC to probe next driver; it would be nicer to put a limit on probing, so after a while it will automatically probe next driver - when probing, some driver fill the screen with "."s, some other with "(probe failed)"s, and so on... more coherence will be appreciated! Thinking that a lot of driver could potentially do the probing, to avoid filling the screen, the best solution could be something like: [3c5x9] Probing.......... [NE] Probing... [SMC9000] Probing........................ [3c529] Probing.......found! - driver probing order: some isa driver doesn't seem to require tons of probe, some other requir it.... driver probing order should be decided with attention, because these latter drivers should be probed after the former - lance driver: can it works in the etherboot.zdsk? I removed it from genrules.pl, otherwise I couldn't compile... - really simple aestethic issue ;o) At the beginning, when it lists all present drivers, plesase separe them with a space! ie: not [3c5x9][smc9000][ne]... but [3c5x9] [smc9000] [ne] ... ...simply more readable! ;o) - in etherboot.zdsk it seems to me there are image not really useful (like the disk driver or the skeleton...); they could be eliminated from the etherboot build script - etherboot-pci.zdsk seems to try anyway to probe ISA card... not nice This is all... I hope that some of my suggestions would help etherboot to become an even better project! Bye! Paolo |
|
From: rimy2000 <rim...@ho...> - 2003-09-13 02:24:51
|
SGkga2VuLA0KICAgUHJldmlvdXMgZGlmZiBmaWxlIGlzIG5vdCBkaWZmIG92ZXIgdGhlIG9yaWdp bmFsIDUuMy4xIHNvdXJjZSwgaXQgaXMgZGlmZiBvdmVyIDUuMy4xK3lvdXIgZml4ZXMgbWVudGlv bmVkIGluIHByZXZpb3VzIHBvc3Q6DQo+TG9va2luZyBhdCB0aGUgZmlsZSwgSSB3b3VsZCBqdXN0 IGRlbGV0ZSBsaW5lIDEuDQo+QWxzbyBsaW5lIDI2OSBzaG91bGQgYmUgKGV4dHJhICYpOg0KDQo+ KmVwID0gdmlydF90b19waHlzKCZCb290QXJncyk7DQoNCkF0dGFjaG1lbnQgaXMgdGhlIG5ldyBk aWZmIGZpbGUgd2hpY2ggaXMgZGlmZiBvdmVyICA1LjMuMSBzb3VyY2UgZGlyZWN0bHkgYW5kIEkg bWFkZSBjb2RlIGNsZWFuLiBCeSB0aGUgd2F5LCAgd2luY2VfbG9hZGVyLmMoYW5kIG90aGVyIGxv YWRlcnMpIGlzIGluY2x1ZGVkIGluIG9zbG9hZGVyLmMsICBidXQgaW4gY3VycmVudCBtYWtlZmls ZSwgdGhpcyBkZXBlbmRjeSBpcyBub3Qgc2V0LiBUaGVuIGlmIHdlIGNoYW5nZSB3aW5jZV9sb2Fk ZXIuYywgZG8gIm1ha2UgdGhlTklDIiB3aWxsIG5vdCByZWNvbXBpbGUgb3Nsb2FkZXIuYy4gSSBh ZGRlZCB0aGVzZSBsaW5lcyBpbiBNYWtlZmlsZS5tYWluIGFmdGVyIHNlY3Rpb24gZm9yICMgZ2Vu ZXJhbCBydWxlcyBmb3IgY29tcGlsaW5nL2Fzc2VtYmxpbmcgc291cmNlIGZpbGVzOg0KDQojIHNw ZWNpYWwgcnVsZXMgZm9yIGNvbXBpbGluZy9hc3NlbWJsaW5nIHNvdXJjZSBmaWxlcw0KJChCSU4p L29zbG9hZGVyLm86ICAgICAgY29yZS9vc2xvYWRlci5jIGFyY2gvJChBUkNIKS9jb3JlL3dpbmNl X2xvYWRlci5jICQoTUFLRURFUFMpDQogICAgICAgICQoQ0MpICQoQ0ZMQUdTKSAtbyAkQCAtYyAk PA0KDQoNCkNhaSBRaWFuZw0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTog IktlbiBZYXAiIDxrZW5AZXRoZXJib290Lm9yZz4NClRvOiAiRXRoZXJib290IGRldmVsb3BlcnMg bGlzdCIgPGV0aGVyYm9vdC1kZXZlbG9wZXJzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldD4NClNlbnQ6 IFRodXJzZGF5LCBTZXB0ZW1iZXIgMTEsIDIwMDMgMTI6NTcgUE0NClN1YmplY3Q6IFJlOiBbRXRo ZXJib290LWRldmVsb3BlcnNdIFdJTkNFX0lNQUdFIGJ1ZyBmaXhlZA0KDQoNCj4gfEFmdGVyIHNv bWUgbWlub3IgY2hhbmdlcywgdGhlIFdJTkNFX0lNQUdFIGJ1ZyBpbiBWNS4zLjEgZml4ZWQuIEkg Y2FuIGxvYWQgV0lOQ0UgaW1hZ2UgZnJvbSBuZXR3b3JrLg0KPiB8VGhlIG1haW4gY2hhbmdlcyBh cmUNCj4gfDEuICBoYW5kbGUgbm9uIDUxMiBieXRlIHBhY2tldHMNCj4gfDIuIGRidWZmZXIgTVVT VCBiZSBzdGF0aWMNCj4gfA0KPiB8QXR0YWNobWVudCBpcyB0aGUgZGlmZiBmaWxlLg0KPiANCj4g VGhhbmtzLCBuZXcgdmVyc2lvbiB3aWxsIGFwcGVhciBpbiBuZXh0IHJlbGVhc2UgYW5kIHlvdSB3 aWxsIGJlIGNyZWRpdGVkLg0KPiANCj4gDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gVGhpcyBzZi5uZXQgZW1haWwgaXMgc3BvbnNv cmVkIGJ5OlRoaW5rR2Vlaw0KPiBXZWxjb21lIHRvIGdlZWsgaGVhdmVuLg0KPiBodHRwOi8vdGhp bmtnZWVrLmNvbS9zZg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXw0KPiBFdGhlcmJvb3QtZGV2ZWxvcGVycyBtYWlsaW5nIGxpc3QNCj4gRXRoZXJib290 LWRldmVsb3BlcnNAbGlzdHMuc291cmNlZm9yZ2UubmV0DQo+IGh0dHBzOi8vbGlzdHMuc291cmNl Zm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL2V0aGVyYm9vdC1kZXZlbG9wZXJzDQo+IA== |
|
From: <ebi...@ln...> - 2003-09-11 14:05:54
|
ke...@et... (Ken Yap) writes: > >CVS will miss them if you haven't checked them out explicitly and they > >were added by a third party; -d pulls in new directories and -P prunes > >old ones, i.e. where a directory is empty in the checked out version; > >directories never actually die in the CVS repository. > > > >I learned to get in the habit of using "cvs update -dP" > > Aha... > > Eric, could I trouble you to check in the missing stuff in 5.2 or 5.3 > and I will fix it up and schedule a release. I might even be able to > make Marty skip a minor digit. :-) I will take a look. Currently I am working on etherboot mainly as way to review the kernel tg3 driver as I am having with that one. So it depends on how much time I actually have. But I should be able to manage it... Eric |
|
From: <ja...@Mc...> - 2003-09-11 13:28:34
|
On Thu, 11 Sep 2003, Ken Yap wrote: > >I am starting to update my tree from etherboot 5.1 to 5.2 and > >by just diffing the trees I have found several missing directories. > > > >Obviously it is not heavily used code but it is significant. > > > >The UNDI driver to make use of the pre build PXE stack has been deleted. > >And some of the ia64 code as well. > > > >Unless these were deliberate deletions it looks like we need to move > >some more code from 5.1 to 5.2. > > Not deliberate. I couldn't find Michael Brown's UNDI driver when I went > looking. Maybe I didn't update my tree before closing 5.1. Can you tell > me where the missing files are on the Sourceforge CVS and I'll fix? > > I'm not sure, but I think sometimes an update misses new directories in > CVS. Either that, or once you've missed it, it never tells you again. Are you doing 'cvs update -d' ? That's the only way it will pick up new directories. Jim. |
|
From: <ke...@et...> - 2003-09-11 11:10:29
|
>CVS will miss them if you haven't checked them out explicitly and they >were added by a third party; -d pulls in new directories and -P prunes >old ones, i.e. where a directory is empty in the checked out version; >directories never actually die in the CVS repository. > >I learned to get in the habit of using "cvs update -dP" Aha... Eric, could I trouble you to check in the missing stuff in 5.2 or 5.3 and I will fix it up and schedule a release. I might even be able to make Marty skip a minor digit. :-) |
|
From: <prl...@sy...> - 2003-09-11 09:36:28
|
[Resent, first try was from the wrong persona] > I'm not sure, but I think sometimes an update misses new directories in > CVS. Either that, or once you've missed it, it never tells you again. CVS will miss them if you haven't checked them out explicitly and they were added by a third party; -d pulls in new directories and -P prunes old ones, i.e. where a directory is empty in the checked out version; directories never actually die in the CVS repository. I learned to get in the habit of using "cvs update -dP" |
|
From: <ke...@et...> - 2003-09-11 06:06:59
|
>I am starting to update my tree from etherboot 5.1 to 5.2 and >by just diffing the trees I have found several missing directories. > >Obviously it is not heavily used code but it is significant. > >The UNDI driver to make use of the pre build PXE stack has been deleted. >And some of the ia64 code as well. > >Unless these were deliberate deletions it looks like we need to move >some more code from 5.1 to 5.2. Not deliberate. I couldn't find Michael Brown's UNDI driver when I went looking. Maybe I didn't update my tree before closing 5.1. Can you tell me where the missing files are on the Sourceforge CVS and I'll fix? I'm not sure, but I think sometimes an update misses new directories in CVS. Either that, or once you've missed it, it never tells you again. |
|
From: <ke...@et...> - 2003-09-11 04:58:43
|
|After some minor changes, the WINCE_IMAGE bug in V5.3.1 fixed. I can load WINCE image from network. |The main changes are |1. handle non 512 byte packets |2. dbuffer MUST be static | |Attachment is the diff file. Thanks, new version will appear in next release and you will be credited. |
|
From: <ebi...@ln...> - 2003-09-11 03:37:55
|
I am starting to update my tree from etherboot 5.1 to 5.2 and by just diffing the trees I have found several missing directories. Obviously it is not heavily used code but it is significant. The UNDI driver to make use of the pre build PXE stack has been deleted. And some of the ia64 code as well. Unless these were deliberate deletions it looks like we need to move some more code from 5.1 to 5.2. Ken? Eric |
|
From: rimy2000 <rim...@ho...> - 2003-09-10 11:37:06
|
QWZ0ZXIgc29tZSBtaW5vciBjaGFuZ2VzLCB0aGUgV0lOQ0VfSU1BR0UgYnVnIGluIFY1LjMuMSBm aXhlZC4gSSBjYW4gbG9hZCBXSU5DRSBpbWFnZSBmcm9tIG5ldHdvcmsuDQpUaGUgbWFpbiBjaGFu Z2VzIGFyZQ0KMS4gIGhhbmRsZSBub24gNTEyIGJ5dGUgcGFja2V0cw0KMi4gZGJ1ZmZlciBNVVNU IGJlIHN0YXRpYw0KDQpBdHRhY2htZW50IGlzIHRoZSBkaWZmIGZpbGUuDQoNCkJ5IHRoZSB3YXks IHdoZW4gSSBiZWdhbiB0byB3b3JrIHRoaXMgYWZ0ZXJub29uLCBJIGZvdW5kIG15IGxpbnV4IGNy YXNoLiBCb3RoIEZTIGluIGhkYTIgYW5kIGhkYTMgY2FuJ3QgYmUgcmVjb2duaXplZC4gVGhlIHN1 cGVyYmxvY2sgd2VyZSBjb3JydXB0LiBJdCB0b29rIG1lIHRoZSB3aG9sZSBhZnRlcm5vb24gdG8g cmVjb3ZlciB0aGUgc3lzdGVtLiBUaGUgbGFzdCB0aGluZyBJIGRpZCBiZWZvcmUgbGludXggY3Jh Y2hlZCBzZWVtcyBpcyBsb2FkaW5nIHRoZSBDRS4gSSBkb24ndCBrbm93IHdoeS4gU28ga2VlcCBh dHRlbnRpb24gd2hlbiB5b3UgdHJ5IGl0ISANCg0KQ2FpIFFpYW5nDQoNCi0tLS0tIE9yaWdpbmFs IE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAiS2VuIFlhcCIgPGtlbkBldGhlcmJvb3Qub3JnPg0KVG86 ICJFdGhlcmJvb3QgZGV2ZWxvcGVycyBsaXN0IiA8ZXRoZXJib290LWRldmVsb3BlcnNAbGlzdHMu c291cmNlZm9yZ2UubmV0Pg0KU2VudDogVHVlc2RheSwgU2VwdGVtYmVyIDA5LCAyMDAzIDEyOjI2 IFBNDQpTdWJqZWN0OiBSZTogW0V0aGVyYm9vdC1kZXZlbG9wZXJzXSBBYm91dCBXSU5DRV9JTUFH RQ0KDQoNCj4gPiAgSSB0cmllZCBodHRwOi8vcm9tLW8tbWF0aWMubmV0LzUuMi4wLyBhbmQgaW4g Y29uZmlndXJlIEkgdW5jaGVja2VkPTIwDQo+ID5FTEZfSU1BR0UgYW5kIGNoZWNrZWQgV0lOQ0Vf SU1BR0UgYnV0IGl0IGJ1aWxkIGZhaWxlZC4gSSBjaGFuZ2VkICJDaG9vc2U9MjANCj4gPlJPTSBv dXRwdXQgZm9ybWF0IiBmcm9tIC5lbGYgdG8gLnpweGUgaXQgYWxzbyAgQnVpbGQgRmFpbGVkLg0K PiA+DQo+ID5JbiBmaWxlIGluY2x1ZGVkIGZyb20gY29yZS9vc2xvYWRlci5jOjc3Og0KPiA+YXJj aC9pMzg2L2NvcmUvd2luY2VfbG9hZGVyLmM6Njc6IGNvbmZsaWN0aW5nIHR5cGVzIGZvciBgY2Vf bG9hZGVyJw0KPiA+YXJjaC9pMzg2L2NvcmUvd2luY2VfbG9hZGVyLmM6MTogcHJldmlvdXMgZGVj bGFyYXRpb24gb2YgYGNlX2xvYWRlcicNCj4gDQo+IFRoaXMgYXBwZWFycyB0byBiZSB0aGUgZmF0 YWwgZXJyb3IsIGl0IGxvb2tzIGxpa2UgNS4yIHdhcyBub3QgdmVyaWZpZWQNCj4gd2l0aCAtRFdJ TkNFX0lNQUdFLiBMb29raW5nIGF0IHRoZSBmaWxlLCBJIHdvdWxkIGp1c3QgZGVsZXRlIGxpbmUg MS4NCj4gQWxzbyBsaW5lIDI2OSBzaG91bGQgYmUgKGV4dHJhICYpOg0KPiANCj4gKmVwID0gdmly dF90b19waHlzKCZCb290QXJncyk7DQo+IA0KPiBXaXRoIHRoZXNlIHR3byBjaGFuZ2VzIGl0IGNv bXBpbGVzLiAgQnV0IHlvdSB3b3VsZCBuZWVkIGEgZGV2ZWxvcG1lbnQNCj4gZW52aXJvbm1lbnQg KGkuZS4gYSBMaW51eCBtYWNoaW5lKSB0byBjb21waWxlIGl0IHlvdXJzZWxmLiBPciB3YWl0IGZv cg0KPiA1LjIuMiBvciA1LjMuMiBvbiByb20tby1tYXRpYy5uZXQsIHdoaWNoZXZlciBjb21lcyBm aXJzdC4gVGhhbmtzIGZvcg0KPiBoaWdobGlnaHRpbmcgdGhlIGVycm9ycy4NCj4gDQo+IA0KPiAt LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ IFRoaXMgc2YubmV0IGVtYWlsIGlzIHNwb25zb3JlZCBieTpUaGlua0dlZWsNCj4gV2VsY29tZSB0 byBnZWVrIGhlYXZlbi4NCj4gaHR0cDovL3RoaW5rZ2Vlay5jb20vc2YNCj4gX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gRXRoZXJib290LWRldmVsb3Bl cnMgbWFpbGluZyBsaXN0DQo+IEV0aGVyYm9vdC1kZXZlbG9wZXJzQGxpc3RzLnNvdXJjZWZvcmdl Lm5ldA0KPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9ldGhl cmJvb3QtZGV2ZWxvcGVycw0KPiA= |
|
From: <ebi...@ln...> - 2003-09-10 00:22:35
|
"Timothy Legge" <tl...@ro...> writes: > > Load a kernel in the Windows CE format (that is Windows CE). > > > > There are obviously a few people doing embedded projects for whom this > > is desirable. > > Ah, so it is loading a Linux kernel on a CE device. You could do that but in most cases it is simply a WINCE kernel. If we can do it easily in etherboot and the code will compile out why not? > I have an issue at > work where loading a CE rom image on a laptop would be useful... I don't know if this would help. Eric |
|
From: Timothy L. <tl...@ro...> - 2003-09-09 23:58:01
|
> Load a kernel in the Windows CE format (that is Windows CE). > > There are obviously a few people doing embedded projects for whom this > is desirable. Ah, so it is loading a Linux kernel on a CE device. I have an issue at work where loading a CE rom image on a laptop would be useful... |
|
From: Timothy L. <tl...@ro...> - 2003-09-09 23:52:19
|
Hi I have confirmed that VMWare 4.0.1 build-5289 seems to work correctly with Etherboot 5.2.1 using the pcnet32 driver. There seems to be an issue if the driver is not relocated, but I will try to resolve that before the evaluation key runs out. I did not have to do the workaround that Llu'is Batlle i Rossell reported with 4.0 build 4460. As a point of interest, it also works with Multicast. If you have an older version of VMWare that does not work with Etherboot 5.2, the best I can say is to either upgrade to a newer version or go bother technical support at VMWare. ;-) Tim Legge |
|
From: <ebi...@ln...> - 2003-09-09 15:10:48
|
"Timothy Legge" <tl...@ro...> writes: > > It may be worth putting the code in to check wince checksums as that > > is not present. > > > > The best suspect at the moment is the wince loader itself. > > As a point of interest, what exactly does the WINCE support allow one to > do? Load a kernel in the Windows CE format (that is Windows CE). There are obviously a few people doing embedded projects for whom this is desirable. Eric |
|
From: Timothy L. <tl...@ro...> - 2003-09-09 14:27:46
|
FYI, EB is reported to work in 5.2 with VMWare > > From: Llu'is Batlle i Rossell > Date: 2003/09/09 Tue PM 02:23:01 GMT > To: Timothy Legge <tl...@ro...> > Subject: Re: Re: Etherboot and Vmware > > On Tue, Sep 09, 2003 at 11:49:06AM +0000, Timothy Legge wrote: > > > > So were you getting an error message that complained that the image was an unsupported OS like OS/2 before you added the zeros? > > > > Tim > > > > Hmmm no. The characters that appear in the screen are: > > ------------- I start typing after this line -------- > Loading ROM image.. > 0200 AX:0212 BX:2200 CX:0001 DX:0100 > . > 0200 AX:0212 BX:2200 CX:0001 DX:0100 > . > 0200 AX:0212 BX:2200 CX:0001 DX:0100 > . > 0200 AX:0212 BX:2200 CX:0001 DX:0100 > . > ---------- And those two repeated lines keep repeating indefinitely ----- > > ----- (After some tries) > > I've noticed that what I told you about sector size wasn't true. Here comes what > I think: > > I've seen that the dots after "Loading ROM image" have been increased in number > when I was making the floppy image grow. > > So I suppose that the piece of code that loads the ROM code from the floppy > tries to read lots of Kb of the floppy. Maybe the whole floppy.... I'll stop > checking for the file size needed by now; you have the code which loads your > etherboot code. > > VMWare BIOS floppy disk read functions may report a Floppy Read Error when it > tries to read a position which isn't in the file (i.e. you have a floppy image > smaller than a real floppy). > > > I'm not very good in English... but the problem is that the code which loads > etherboot code from floppy reads the whole floppy disk, even if it doesn't need > to. If you copy the > small floppy boot code into a real floppy disk, the whole floppy disk will be > readable. But that isn't true if you try to load the .fdsk file as a floppy > image using vmware. So you need a floppy image as large as a floppy disk to boot > from vmware. Nothing more. :) I might not be using correct English, because the > entire 'small' problem shout be obvious. :) > > > Now I'll try new pcnet32 driver... > > OH! pcnet32 driver works perfectly! Well, right now I have the tftp server down, > but it catches the dhcp reply. (It didn't using lancepci driver). > > You can add this 'vote' in etherboot section for me if you want. Otherwise > notice me and I will. > > So, vmware 4.0 build 4460 boots from EB 5.2.1 pcnet32 driver. Of course, the > only way of booting EB in vmware is using floppy, as you don't have access to > any ROM of the ethernet device (it's emulated!). But you can have the contents > of the bootable floppy in a floppy image: an image that has to be 'one floppy' > long: 80*2*18*512 = 1474560 long > (that is determined by the code which loads EB from floppy (i.e. the very first > code-bytes of the floppy image)) > > > Ok... ask me whatever more you need. :) > > Thanks! |
|
From: ron m. <rmi...@la...> - 2003-09-09 14:04:20
|
On Tue, 9 Sep 2003, Timothy Legge wrote: > As a point of interest, what exactly does the WINCE support allow one to > do? if your machine seems to be running too fast, and not crashing often enough, then WINCE support will allow you to pay money to microsoft for the privelege of solving those too problems. ron |
|
From: Timothy L. <tl...@ro...> - 2003-09-09 10:20:09
|
Hi Marty It may be a good idea to update Rom-o-matic with 5.2.1. People are attempting to use the lance driver with 5.2 and probably do no know enough to disable relocation. The pcnet32 driver is only available in 5.2.1 and I believe that Ken now prevents the lance from compiling. Tim |
|
From: Timothy L. <tl...@ro...> - 2003-09-09 10:12:08
|
> It may be worth putting the code in to check wince checksums as that > is not present. > > The best suspect at the moment is the wince loader itself. As a point of interest, what exactly does the WINCE support allow one to do? Tim |
|
From: <ebi...@ln...> - 2003-09-09 09:14:10
|
"elife elife" <rim...@ho...> writes: > Hi, > I built 5.3.1 (fixed it according your comments), but encountered a > problem: //------------------------------------------------- > ... [snip] > Searching for server (DHCP)... > ..Me: 172.27.4.250, Server: 172.27.4.23, Gateway 172.27.4.23 > Loading 172.27.4.23:nk.bin ...(WINCE)String Physical Address = > 00220000 Image Size = 5486872 [0053b918] [snip] > Searching for server (DHCP)... > ..Me: 172.27.4.250, Server: 172.27.4.23, Gateway 172.27.4.23 > Loading 172.27.4.23:nk.bin ...(WINCE) > segment [07FF8300,CF8AC173) does not fit in any memory region > <abort> > //--------------------------------------------------------------- > > I wonder what's the meaning of "segment [xxxxxxxx, xxxxxxxx) does > not fit in any memory region" and where is the problem: linuxbios or > etherboot? etherboot has a generic function prep_segment that checks to see if a section of a file will fit in memory. The addresses are the starting and ending physical addresses of that chunk of file. So on the face of it what is happening is the wince image is trying to load into a memory location that you don't have on your machine. However the fact that you are not getting the same results consistently looks like something else is happening. (The messages from attempting to load nk.bin are different the second time etherboot tries). Something is clearly getting corrupted. It may be worth putting the code in to check wince checksums as that is not present. The best suspect at the moment is the wince loader itself. Eric |
|
From: elife e. <rim...@ho...> - 2003-09-09 07:18:07
|
Hi,
I built 5.3.1 (fixed it according your comments), but encountered a
problem:
//-------------------------------------------------
...
Welcome to elfboot, the open sourced starter.
January 2002, Eric Biederman.
Version 1.2
37:init_bytes() - zkernel_start:0xfff00000 zkernel_mask:0x0000ffff
Found ELF candiate at offset 0
Loading Etherboot version: 5.3.1
Dropping non PT_LOAD segment
New segment addr 0x20000 size 0xf084 offset 0xb0 filesize 0x5560
(cleaned up) New segment addr 0x20000 size 0xf084 offset 0xb0 filesize
0x5560
Loading Segment: addr: 0x0000000003b83668 memsz: 0x000000000000f084 filesz:
0x0000000000005560
Clearing Segment: addr: 0x0000000003b88bc8 memsz: 0x0000000000009b24
Jumping to boot code at 0x20000
ROM segment 0x8655 length 0x0280 reloc 0x00020000
CPU 203 Mhz
Etherboot 5.3.1 (GPL) http://etherboot.org Tagged WINCE for [RTL8139]
Relocating _text from: [00020000,00030090) to [03aeff70,03b00000)
Boot from (N)etwork or (Q)uit?
robing pci nic...
[rtl8139] - ioaddr 0X1000, addr 00:E0:4C:6D:01:CA 10Mbps half-duplex
Searching for server (DHCP)...
..Me: 172.27.4.250, Server: 172.27.4.23, Gateway 172.27.4.23
Loading 172.27.4.23:nk.bin ...(WINCE)String Physical Address = 00220000
Image Size = 5486872 [0053b918]
Section Address = [00220000]
Size = 16 [00000010]
Checksum = 2088 [00000828]
Section Address = [00220040]
Size = 8 [00000008]
Checksum = 703 [000002bf]
Section Address = [00221000]
Size = 452608 [0006e800]
Checksum = 46064418 [02bee322]
....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
segment [FF83C033,C017CF3A) does not fit in any memory region
<abort>
Probing pci nic...
Probing isa nic...
<sleep>
Boot from (N)etwork or (Q)uit?
Probing pci nic...
[rtl8139] - ioaddr 0X1000, addr 00:E0:4C:6D:01:CA 10Mbps half-duplex
Searching for server (DHCP)...
..Me: 172.27.4.250, Server: 172.27.4.23, Gateway 172.27.4.23
Loading 172.27.4.23:nk.bin ...(WINCE)
segment [07FF8300,CF8AC173) does not fit in any memory region
<abort>
Probing pci nic...
Probing isa nic...
<sleep>
//---------------------------------------------------------------
I wonder what's the meaning of "segment [xxxxxxxx, xxxxxxxx) does not
fit in any memory region" and where is the problem: linuxbios or etherboot?
Thanks!
>From: ke...@et... (Ken Yap)
>Reply-To: Etherboot developers list
<eth...@li...>
>To: Etherboot developers list <eth...@li...>
>Subject: Re: [Etherboot-developers] About WINCE_IMAGE
>Date: Tue, 09 Sep 2003 14:26:29 +1000
>
> > I tried http://rom-o-matic.net/5.2.0/ and in configure I unchecked=20
> >ELF_IMAGE and checked WINCE_IMAGE but it build failed. I changed
"Choose=20
> >ROM output format" from .elf to .zpxe it also Build Failed.
> >
> >In file included from core/osloader.c:77:
> >arch/i386/core/wince_loader.c:67: conflicting types for `ce_loader'
> >arch/i386/core/wince_loader.c:1: previous declaration of `ce_loader'
>
>This appears to be the fatal error, it looks like 5.2 was not verified
>with -DWINCE_IMAGE. Looking at the file, I would just delete line 1.
>Also line 269 should be (extra &):
>
> *ep = virt_to_phys(&BootArgs);
>
>With these two changes it compiles. But you would need a development
>environment (i.e. a Linux machine) to compile it yourself. Or wait for
>5.2.2 or 5.3.2 on rom-o-matic.net, whichever comes first. Thanks for
>highlighting the errors.
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Etherboot-developers mailing list
>Eth...@li...
>https://lists.sourceforge.net/lists/listinfo/etherboot-developers
_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn
|
|
From: <ebi...@ln...> - 2003-09-09 04:34:23
|
ke...@et... (Ken Yap) writes: > >Hi, > > In Config it says > > "-D WINCE_IMAGE > > Add the ability to boot WINCE.... now only sis630 OK! " > > If I want to add WINCE_IMAGE support in other mainboards, what should I> > >do? > > I suspect it means that the person who added the code only tested it > with the SiS630. I see no reason why an image format should be specific > to a particular NIC, all the Etherboot drivers offer the same API to the > core code. Right but the SIS630 is a particular SIS chipset. I think there were some interesting video dependencies. > So give it a try and let us know if it works with other NICs. > If it does I'll remove that comment. I was trying to merge one of the variants of etherboot that was generated by the people doing LinuxBIOS. Ollie Lho in this case. The code is more or less correct but obviously something got messed up. I did not have the ability to test it. I don't think it would take much to fix up for someone who has a test case. Eric |
|
From: <ke...@et...> - 2003-09-09 04:26:53
|
> I tried http://rom-o-matic.net/5.2.0/ and in configure I unchecked=20 >ELF_IMAGE and checked WINCE_IMAGE but it build failed. I changed "Choose=20 >ROM output format" from .elf to .zpxe it also Build Failed. > >In file included from core/osloader.c:77: >arch/i386/core/wince_loader.c:67: conflicting types for `ce_loader' >arch/i386/core/wince_loader.c:1: previous declaration of `ce_loader' This appears to be the fatal error, it looks like 5.2 was not verified with -DWINCE_IMAGE. Looking at the file, I would just delete line 1. Also line 269 should be (extra &): *ep = virt_to_phys(&BootArgs); With these two changes it compiles. But you would need a development environment (i.e. a Linux machine) to compile it yourself. Or wait for 5.2.2 or 5.3.2 on rom-o-matic.net, whichever comes first. Thanks for highlighting the errors. |
|
From: elife e. <rim...@ho...> - 2003-09-09 04:07:55
|
Hi, I tried http://rom-o-matic.net/5.2.0/ and in configure I unchecked ELF_IMAGE and checked WINCE_IMAGE but it build failed. I changed "Choose ROM output format" from .elf to .zpxe it also Build Failed. Thanks! rtl8139.elf Build Failed -------------------------------------------------------------------------------- Build failed. Status = 2. Following is the output from make: make: Entering directory `/tmp/ROMgcjfq5' gcc -DLINUXBIOS -DCONFIG_PCI_DIRECT -DCONFIG_TSC_CURRTICKS -fstrength-reduce -fomit-frame-pointer -mcpu=i386 -march=i386 -malign-jumps=1 -malign-loops=1 -malign-functions=1 -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DWINCE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCONSOLE_SERIAL -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DCOMPRESERVE -DRELOCATE -DCONFIG_PCI -DCONFIG_ISA -Os -ffreestanding -Wall -W -Wno-format -DVERSION_MAJOR=5 -DVERSION_MINOR=2 -DVERSION=\"5.2.0\" -DRELOC=0x20000 -I include -I arch/i386/include -DARCH=i386 -DINCLUDE_RTL8139 -o bin/rtl8139.o -c drivers/net/rtl8139.c cc1: warning: -malign-loops is obsolete, use -falign-loops cc1: warning: -malign-jumps is obsolete, use -falign-jumps cc1: warning: -malign-functions is obsolete, use -falign-functions gcc -DLINUXBIOS -DCONFIG_PCI_DIRECT -DCONFIG_TSC_CURRTICKS -fstrength-reduce -fomit-frame-pointer -mcpu=i386 -march=i386 -malign-jumps=1 -malign-loops=1 -malign-functions=1 -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DWINCE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCONSOLE_SERIAL -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DCOMPRESERVE -DRELOCATE -DCONFIG_PCI -DCONFIG_ISA -Os -ffreestanding -Wall -W -Wno-format -DVERSION_MAJOR=5 -DVERSION_MINOR=2 -DVERSION=\"5.2.0\" -DRELOC=0x20000 -I include -I arch/i386/include -DARCH=i386 -o bin/linuxbios.o -c firmware/linuxbios/linuxbios.c cc1: warning: -malign-loops is obsolete, use -falign-loops cc1: warning: -malign-jumps is obsolete, use -falign-jumps cc1: warning: -malign-functions is obsolete, use -falign-functions gcc -DLINUXBIOS -DCONFIG_PCI_DIRECT -DCONFIG_TSC_CURRTICKS -fstrength-reduce -fomit-frame-pointer -mcpu=i386 -march=i386 -malign-jumps=1 -malign-loops=1 -malign-functions=1 -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DWINCE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCONSOLE_SERIAL -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DCOMPRESERVE -DRELOCATE -DCONFIG_PCI -DCONFIG_ISA -Os -ffreestanding -Wall -W -Wno-format -DVERSION_MAJOR=5 -DVERSION_MINOR=2 -DVERSION=\"5.2.0\" -DRELOC=0x20000 -I include -I arch/i386/include -DARCH=i386 -o bin/main.o -c core/main.c cc1: warning: -malign-loops is obsolete, use -falign-loops cc1: warning: -malign-jumps is obsolete, use -falign-jumps cc1: warning: -malign-functions is obsolete, use -falign-functions core/main.c: In function `main': core/main.c:147: warning: unused parameter `ptr' core/main.c: In function `main_loop': core/main.c:296: warning: comparison between signed and unsigned gcc -DLINUXBIOS -DCONFIG_PCI_DIRECT -DCONFIG_TSC_CURRTICKS -fstrength-reduce -fomit-frame-pointer -mcpu=i386 -march=i386 -malign-jumps=1 -malign-loops=1 -malign-functions=1 -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DWINCE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCONSOLE_SERIAL -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DCOMPRESERVE -DRELOCATE -DCONFIG_PCI -DCONFIG_ISA -Os -ffreestanding -Wall -W -Wno-format -DVERSION_MAJOR=5 -DVERSION_MINOR=2 -DVERSION=\"5.2.0\" -DRELOC=0x20000 -I include -I arch/i386/include -DARCH=i386 -o bin/osloader.o -c core/osloader.c cc1: warning: -malign-loops is obsolete, use -falign-loops cc1: warning: -malign-jumps is obsolete, use -falign-jumps cc1: warning: -malign-functions is obsolete, use -falign-functions In file included from core/osloader.c:77: arch/i386/core/wince_loader.c:67: conflicting types for `ce_loader' arch/i386/core/wince_loader.c:1: previous declaration of `ce_loader' In file included from core/osloader.c:77: arch/i386/core/wince_loader.c: In function `wince_probe': arch/i386/core/wince_loader.c:68: warning: unused parameter `len' In file included from core/osloader.c:77: arch/i386/core/wince_loader.c: In function `ce_loader': arch/i386/core/wince_loader.c:76: warning: unused parameter `eof' arch/i386/core/wince_loader.c: In function `jump_2ep': arch/i386/core/wince_loader.c:270: incompatible type for argument 1 of `virt_to_phys' arch/i386/core/wince_loader.c:270: warning: assignment makes pointer from integer without a cast In file included from core/osloader.c:85: arch/i386/core/tagged_loader.c: In function `tagged_download': arch/i386/core/tagged_loader.c:136: warning: passing arg 3 of `xstart16' makes pointer from integer without a cast core/osloader.c: In function `prep_segment': core/osloader.c:199: warning: comparison between signed and unsigned make: *** [bin/osloader.o] Error 1 make: Leaving directory `/tmp/ROMgcjfq5' Please let us know that this happened. >From: ke...@et... (Ken Yap) >Reply-To: Etherboot developers list <eth...@li...> >To: Etherboot developers list <eth...@li...> >Subject: Re: [Etherboot-developers] About WINCE_IMAGE >Date: Tue, 09 Sep 2003 13:37:39 +1000 > > >Hi, > > In Config it says > > "-D WINCE_IMAGE > > Add the ability to boot WINCE.... now only sis630 OK! " > > If I want to add WINCE_IMAGE support in other mainboards, what should I> > >do? > >I suspect it means that the person who added the code only tested it >with the SiS630. I see no reason why an image format should be specific >to a particular NIC, all the Etherboot drivers offer the same API to the >core code. So give it a try and let us know if it works with other NICs. >If it does I'll remove that comment. > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Etherboot-developers mailing list >Eth...@li... >https://lists.sourceforge.net/lists/listinfo/etherboot-developers _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn |
53 messages has been excluded from this view by a project administrator.
