etherboot-developers Mailing List for Etherboot (Page 188)
Brought to you by:
marty_connor,
stefanhajnoczi
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: <ke...@et...> - 2003-07-28 02:41:18
|
>I committed another change to the 5.0 (and 5.1) drivers. They now work >in both versions. I had to add a udelay(5) to the Transmit for the >revision 48 card that I have. It only seemed to be required for 5.0 but >I did not bother making it revision or version specific. > >Ken, if you could test the card you have, I would be interested in >knowing whether your card requires the delay in 5.0. Ok, it'll be in about 8 hours time, I don't have the hardware in front of me now. If it works are you happy to let me release 5.0.11 and put 5.0 into maintenance mode? |
|
From: Timothy L. <tl...@ro...> - 2003-07-28 01:12:47
|
Hi I committed another change to the 5.0 (and 5.1) drivers. They now work in both versions. I had to add a udelay(5) to the Transmit for the revision 48 card that I have. It only seemed to be required for 5.0 but I did not bother making it revision or version specific. Ken, if you could test the card you have, I would be interested in knowing whether your card requires the delay in 5.0. Regards, Tim --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 |
|
From: Timothy L. <tl...@ro...> - 2003-07-27 19:07:46
|
Hi I have committed a few more changes to both 5.0 and 5.1. The tlan.c file is exactly the same in each version except for line one which is #define EB50 and #define EB51 in the 5.0 and 5.1 versions respectively. I would like to have used VERSION_MAJOR and VERSION_MINOR to distinguish the versions for compilation but I couldn't figure it out at the time... The only weird thing is that the 5.0 version of the driver requires EBDEBUG to be defined. I have yet to track down the issue but I am sure it is just a matter of time. Tim > -----Original Message----- > From: eth...@li... [mailto:etherboot- > dev...@li...] On Behalf Of Timothy Legge > Sent: Sunday, July 27, 2003 2:14 PM > To: 'Etherboot developers list' > Subject: RE: [Etherboot-developers] tlan driver - Working in 5.1 > > > BTW Timothy, tlan doesn't work without -DRELOCATE, it keeps scrolling > > the screen up. I don't know if it's too big or the address remapping > is > > wrong without relocation. This might affect your ability to run it > under > > 5.0. > > No, I actually fixed the problem in 5.0 and did not realize that I > needed it without -DRELOCATE in 5.1. I have committed the fix. > > Tim > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click- > url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Etherboot-developers mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-developers > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 |
|
From: Timothy L. <tl...@ro...> - 2003-07-27 17:13:52
|
> BTW Timothy, tlan doesn't work without -DRELOCATE, it keeps scrolling > the screen up. I don't know if it's too big or the address remapping is > wrong without relocation. This might affect your ability to run it under > 5.0. No, I actually fixed the problem in 5.0 and did not realize that I needed it without -DRELOCATE in 5.1. I have committed the fix. Tim --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 |
|
From: <ke...@et...> - 2003-07-27 15:44:19
|
>Ok, it's not main.c, it's what happens after returning from main.
>Happens even without -DRELOCATE. Must be a miscalculation of the stack
>contents in the intermediate asm. Dang.
Eric,
Question for you. In start16.S just a few lines down from _start: you
have:
andw $0xffc, %sp /* 32bit align the stack */
Shouldn't that be 0xfffc?
|
|
From: <ke...@et...> - 2003-07-27 14:55:38
|
>Works fine, but now I hit another bug, nothing to do with tlan. L from >the boot prompt blanks the screen and jumps off to hyperspace instead of >returning to the BIOS. This from either boot ROM or floppy. Trying to >figure out the state machine code in main.c. Ok, it's not main.c, it's what happens after returning from main. Happens even without -DRELOCATE. Must be a miscalculation of the stack contents in the intermediate asm. Dang. BTW Timothy, tlan doesn't work without -DRELOCATE, it keeps scrolling the screen up. I don't know if it's too big or the address remapping is wrong without relocation. This might affect your ability to run it under 5.0. |
|
From: <ke...@et...> - 2003-07-27 14:02:43
|
>Ken and Marty, can you do a quick test with you cards? Marty, please >note the revision number of the chip as displayed on screen. If it is >something different than 35 or 48 please let men know. Works fine, but now I hit another bug, nothing to do with tlan. L from the boot prompt blanks the screen and jumps off to hyperspace instead of returning to the BIOS. This from either boot ROM or floppy. Trying to figure out the state machine code in main.c. |
|
From: Timothy L. <tl...@ro...> - 2003-07-27 13:23:21
|
Hi I just checked in some changes to the tlan driver. It now compiles and works fine on tlan cards with revision 35 and 48 chips. I cannot guarantee that it works on anything else. It still needs a little cleanup, but I will first look at syncing the 5.1 and 5.0 driver. Ken and Marty, can you do a quick test with you cards? Marty, please note the revision number of the chip as displayed on screen. If it is something different than 35 or 48 please let men know. Tim --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 |
|
From: <ke...@et...> - 2003-07-27 02:36:51
|
>I just created one on one of my servers, here it is: >http://etherboot.augustinnetz.de/ Thanks, I've linked to it from the doco page in the upcoming 5.2. |
|
From: Anselm M. H. <an...@ho...> - 2003-07-26 18:17:04
|
Hello satadru, === My 2 cents. Not necessarily the opinion of other etherboot developers === > I've been looking at various ways of booting WinPE (Windows > Preinstallation Environment) off of the network, and after searching the > net and the etherboot archives, it seems that the two most viable > methods are setting up a RIS server (ugly) or somehow try to get the RIS > boot disk tagged for etherboot (ugly, especially considering the likely > lack of support for my NIC, the sis900). sis900 not supported by WinPE? Etherboot works fine with it. I even have one here and happily use it some day or another for netbooting. Quting: = WinPE can be booted over the network (using Pre-boot Execution Environment = [PXE] basic input/output system [BIOS] and a Remote Installation Services = [RIS] server) or via a CD. Thus, WinPE can be run without the need for = persistent storage. However, WinPE cannot be booted via Remote Boot Service. This is what a quick search found out for me. Perhaps this can be done with etherboot too. However: = IOS, or by using a remote boot disk for pre-PC98 computers. MS seems to distribute a bootdisk which supports several NICs (via packet drivers?) and allows starting RIS from network. If you can get that disk, try to etherboot an image of that disk. Perhaps it does not work (if the memory the disc is loaded to is overwritten by a program on that disc, who knows), but give it a run and tell us! > I noticed that IBM has some sort of combined implementation of iscsi and > something similar to etherboot: > http://www.haifa.il.ibm.com/projects/storage/iboot/faq.html Quoting: = The remote boot offers a seamless solution; changes to the kernel can be made = permanent. Say, for example, a user wants to add a Linux module to support = new drivers. With existing methods, the module is lost when the computer is = shut down and users have to repeatedly add the module every time they boot = the machine. iBoot is capable of saving these changes, making them permanent. = iBoot also supports a dual boot option. Users are not limited to a single = operating system and can select the desired operating system from a menu = at boot time, offering enhanced flexibility of operation They seem not to know about NFS, and never to have used etherboot menuing facilities. This paragraph simply is marketing blahblah-nonsense. Their technique seems to be to implement a int13 support routine that gets harddisk requests and relays them via network. I don't see why it should not run with DOS/Win9x, but they claim it not do so. Seems not to be too perfect then. > How hard would this be to implement inside etherboot? Open Source iscsi > drivers exist: > What I would like to be able to do is setup a linux box to serve iscsi, > and then use a etherboot boot rom to boot off of that network drive. I don't see sense in here. Why cannot you run a tftp or nfs server? Serving iSCSI surely is the greater security hole than a chroot'ed running tftp server for which the source code is available. Just for loading the kernel and initrd in doubt, as the kernel in turn could load an iSCSI module and then very well access that remote iSCSI server. > Is this too far outside to purview of the etherboot project to be done? If you like to implement it, please do so. *I* certainly won't, and I don't expect the experts around here to do so neither. It would require to implement tcp (at present there only is udp support for good reasons: Much lighter to implement), and after that one could as well use ftp or http to retrieve kernel & initrd. > Etherboot would then have to maintain some process in memory to be able > to communicate with the iscsi server while the machine was running. I don't think so. From what I understood (this may be wrong though), it only needs this stack for "real mode" accesses to iSCSI, like those done by the BIOS (and Win 2k/XP... first stage), lateron the kernel loads an own module, which real-mode-drives the NIC and accesses the iSCSI more directly. Linux kernels are claimed to run without any real mode stack in memory, just from that kernel driver. > This would be Really cool, *not*. Not to much at least. http access in my opinion is much more a attraction bringer. > and would also suddenly make all of those > machines out there with etherboot supported roms iscsi bootable > machines. I haven't seen one iSCSI server yet (well, the protocol is quite fresh), and can't understand why they should be unable to have a tftp server or a NFS server just for booting purposes. > If this isn't possible, does anybody know of a iscsi boot > image that will let me etherboot to a second stage bootloader that would > support iscsi? Nope. But you could ask Intel's :-( if they won't open-source their bootloader some day. OK, bad idea :-/ Hope to help. Anselm Martin Hoffmeister Stockholm Projekt Computer-Service <an...@ho...> -- Disclaimer - These opiini^H^H damn! ^H^H ^Q ^[ .. :w :q :wq :wq! ^d X^? exit X Q ^C ^c ^? :quitbye CtrlAltDel ~~q :~q logout save/quit :!QUIT ^[zz ^[ZZZZZZ ^H man vi ^@ ^L ^[c ^# ^E ^X ^I ^T ? help helpquit ^D ^d man help ^C exit ?Quit ?q CtrlShftDel "Hey, what does this button d..." |
|
From: Anselm M. H. <an...@ho...> - 2003-07-26 17:15:56
|
Hello Ken, > Something worth thinking about post-5.2 is setting up an Etherboot wiki. > Tips like Marty's posting about flashing NICs belong in a wiki, as do > some of the short manuals currently in CVS; the conventional manual > publishing process is too slow for changing content. It will also allow > us to capture more of the knowledge that's in the heads of the users out > there. I just created one on one of my servers, here it is: http://etherboot.augustinnetz.de/ There's nothing in there yet of course, but wait and see :-) Best regards, Anselm Martin Hoffmeister Stockholm Projekt Computer-Service <an...@ho...> -- Disclaimer - These opiini^H^H damn! ^H^H ^Q ^[ .. :w :q :wq :wq! ^d X^? exit X Q ^C ^c ^? :quitbye CtrlAltDel ~~q :~q logout save/quit :!QUIT ^[zz ^[ZZZZZZ ^H man vi ^@ ^L ^[c ^# ^E ^X ^I ^T ? help helpquit ^D ^d man help ^C exit ?Quit ?q CtrlShftDel "Hey, what does this button d..." |
|
From: <ke...@et...> - 2003-07-26 14:43:28
|
Something worth thinking about post-5.2 is setting up an Etherboot wiki. Tips like Marty's posting about flashing NICs belong in a wiki, as do some of the short manuals currently in CVS; the conventional manual publishing process is too slow for changing content. It will also allow us to capture more of the knowledge that's in the heads of the users out there. |
|
From: <ke...@et...> - 2003-07-26 12:07:53
|
What I've been doing with the 5.2 documentation in the CVS: I've fixed up all the content so that it's XML (as XML is also SGML, sgmltools-lite doesn't mind). This allows well-formedness to be checked with tidy -e -xml. I've updated the structure to be Docbook 4.2. I've merged security and vendortags into userman as appendices, and spec and *compressor into devman as appendices. This reduces the number of documents by 5. oldREADME, atnetboot and 16 are gone. I've been trying out a free XML editor from Morphon (www.morphon.com). It keeps the document syntax conformant to the DTD and provides a rough view of it using CSS. However as it's written in Java and uses swing, it isn't the snappiest. There's another problem and that is the editor might write things out with its own idea of whitespacing. It's still the same XML, but cvs will think there are big differences because the differencing is line oriented. So for the time being we should stick to using text editors to edit the content and use tidy and morphon to check. I might run the content through tidy soon, the conversion from linuxdoc resulted in some rather strange indentation. Now to bring the words up to date with reality. |
|
From: <ke...@et...> - 2003-07-25 23:56:31
|
>methods are setting up a RIS server (ugly) or somehow try to get the RIS >boot disk tagged for etherboot (ugly, especially considering the likely >lack of support for my NIC, the sis900). =20 Have you looked? There is a sis900 driver. >Is this too far outside to purview of the etherboot project to be done?=20 >Etherboot would then have to maintain some process in memory to be able >to communicate with the iscsi server while the machine was running. Etherboot gets displaced by whatever it's loading so it cannot "maintain some process in memory". I don't know how feasible it is to boot off iscsi. It may require a more complex network stack, i.e. TCP, than Etherboot has. |
|
From: satadru p. <sa...@um...> - 2003-07-25 20:37:56
|
I've been looking at various ways of booting WinPE (Windows Preinstallation Environment) off of the network, and after searching the net and the etherboot archives, it seems that the two most viable methods are setting up a RIS server (ugly) or somehow try to get the RIS boot disk tagged for etherboot (ugly, especially considering the likely lack of support for my NIC, the sis900). =20 I noticed that IBM has some sort of combined implementation of iscsi and something similar to etherboot: http://www.haifa.il.ibm.com/projects/storage/iboot/faq.html How hard would this be to implement inside etherboot? Open Source iscsi drivers exist: http://sourceforge.net/project/showfiles.php?group_id=3D23858&release_id=3D= 133985 and here: http://linux-iscsi.sourceforge.net/ What I would like to be able to do is setup a linux box to serve iscsi, and then use a etherboot boot rom to boot off of that network drive. Is this too far outside to purview of the etherboot project to be done?=20 Etherboot would then have to maintain some process in memory to be able to communicate with the iscsi server while the machine was running. This would be Really cool, and would also suddenly make all of those machines out there with etherboot supported roms iscsi bootable machines. If this isn't possible, does anybody know of a iscsi boot image that will let me etherboot to a second stage bootloader that would support iscsi? satadru InterCooperative Council at the University of Michigan |
|
From: <ke...@et...> - 2003-07-24 06:13:56
|
I have released Etherboot 5.1.9 at http://www.etherboot.org/ This release brings us closer to the 5.2 release. Please try it out and let know us via the mailing list any problems you encounter. Before it becomes an FAQ, please note that you must use LTSP kernel-3.0.10 or later with Etherboot 5.1. If you wish to use an older LTSP kernel with 5.1/5.2 you have to retag the boot image, using the tools in ltsp_initrd_kit and mknbi-1.4. Not just LTSP kernels but any Linux kernels tagged with old mknbi's must be retagged, there is a bug in old mknbi's. Changes from 5.1.8: + Fix for correct SMC8416 detection. + Alignment bug fix for the 3c90x driver contributed by Neil Newell. + Robb Main found a bug in appending the MACHINE_INFO to the DHCP request. + SONE Takeshi fixed the Multiboot structure. + Patch from Axel Dittrich to allow timeout to be changed to a fixed value for peer-to-peer setups where the exponential backoff is not suitable. + Tlan driver contributed by Timothy Legge. + Support for symlinks on NFS mounts by Anselm Martin Hoffmeister. + Experimental safe booting code by Anselm Martin Hoffmeister. + Run Etherboot in an even megabyte so that unsetting A20 won't kill it. Experimental UNDI driver by Michael Brown. MD5 sums: 83854d11d6381512ed3ddac7d531f363 etherboot-5.1.9.tar.bz2 0009deb893e9c1c2c976478e99c5dfab etherboot-5.1.9.tar.gz SHA1 sums: 673acba9051c50116b57d0039436e74a52ad9dc3 etherboot-5.1.9.tar.bz2 51e90ed3eeb0e170812482b89ffa20ca21dbf0ea etherboot-5.1.9.tar.gz |
|
From: Hans-Peter J. <hp...@ur...> - 2003-07-22 17:33:16
|
Hi, after experimenting with gfxboot from suse 8.2 a bit, I'm able to run successfully a customized graphical grub menu via network eb and pxe loaders. Nice! Currently, my primary concern is netbooting some dos images (generated with mknbi-dos). This is somewhat important here, since we use them also for bios and bootrom flashing (e.g. e1000) in our diskless env. Can someone give me a start on tackling this? The way to load/exec those images in grub differs a lot from etherboot. Any help is highly appreciated. I've also managed to add a eb 5.1.18 based e1000 driver with some medium invasive patches to netboot/*.. Should I post them here for discussion? Cheers, Pete |
|
From: Hans-Peter J. <hp...@ur...> - 2003-07-22 17:29:20
|
Hi Axel, sorry for the huge delay (holiday related)... Finally I got around to test your patches. They run smoothly with my adapters, too. Nice work. Thanks a lot. I also managed to port your driver port to grub 0.93. After experimenting with gfxboot from suse 8.2 a bit, I'm able to run a customized graphical grub menu via network from eb and pxe loaders successfully. Interested? Thanks again & best regards, Pete On Friday 04 July 2003 15:36, Axel Dittrich wrote: > Hallo, > > this answer is especially for Hans-Peter Jansen (see archive > 2003-06-17 09:25) > > I'm not a member of this list but have done a e1000 driver backport > from 5.1.8 to 5.0.10. > > It works very well for me with e new 82540EM (PCI ID: 0x8086/0x100E) > , so have a look on it: > > For comments please write to me directly. > > Axel > > (See attached file: etherboot-5.0.10.e1000-patch) |
|
From: <ke...@et...> - 2003-07-22 00:06:23
|
>I have released mknbi-1.4.1 at http://www.etherboot.org >... >+ Quick and dirty Perl script to convert NBI Linux images to ELF. I discovered that the RPM was missing this file so I've rereleased the RPM and SRPM. The tarball is not affected so if you are building from source you don't have to fetch anything. To update the RPM, just do a rpm -Fhv mknbi-1.4.1-2.noarch.rpm and it will replace 1.4.1-1. MD5 sums: a462794d4bb2e25a892a8e4c1f92f768 mknbi-1.4.1-2.noarch.rpm 81f34ff8daa0254d1f5c35011b46f296 mknbi-1.4.1-2.src.rpm |
|
From: Georg B. <Geo...@po...> - 2003-07-21 19:03:09
|
Am Montag, 21. Juli 2003 07:56 schrieb Richard Jelinek: > Very well then. 500US$ for the port within one week, 1000US$ for the > port "now" ~24hr so that the X5DPA-GG boots successfully. I could do that (but not the "now" option), provided I'll get access to the hardware. I just updated the patch under http://sourceforge.net/tracker/index.php?func=detail&aid=728012&group_id=4233&atid=304233 to work with current cvs. Try this first, it might work since I added all new variants of the Linux 2.4.21 driver in april, and yours is amongst them. So the Etherboot community reaction time might be negative in this case ;-) The only reason for the patch not being included in 5.1cvs is that there were some reorganisations in the driver and I did not want to break anything for already supported cards. Georg |
|
From: Richard J. <rj...@pe...> - 2003-07-21 05:56:42
|
On Mon, Jul 21, 2003 at 03:37:01PM +1000, Ken Yap wrote:
> >I'm searching for an Etherboot lzpxe Image with support for the Intel
> >82541EI chipset. This chipset happens to be on the Supermicro X5DPA-G
> >and GG motheroards.
> >
> >It seems I really need exactly THIS chipset supported, as Etherboot
> >won't work with just a "similar" chipset chosen. Is there any support
> >(planned). What can I do to let support happen?
>
> According to the Linux driver the 82541 support was added there in March
> 2003. Etherboot's driver was based on an earlier version ported by
> Chris Li, and fixed by Eric Biederman. AFAIK nobody has ported that
> 82541 part of the driver to Etherboot yet, although Georg Baum did some
> work on the 82547, which is in the patch area.
>
> I can see a few ways you can proceed, here are some. 1. You could hack
> the code yourself and send the changes to us when you get it to work.
> 2. You could offer someone money to work on the 82541 code. 3. You
> could ask Intel to do the port, but they would probably just suggest 2.
>
> [Thread redirected to -developers.]
Very well then. 500US$ for the port within one week, 1000US$ for the
port "now" ~24hr so that the X5DPA-GG boots successfully.
+ a huge positive publicity about reaction times of the OSS
comunity. ;-)
--
best regards,
Dipl.-Inf. Richard Jelinek
- The PetaMem Group - Prague/Nuremberg - www.petamem.com -
-= 3394928 Mind Units =-
|
|
From: <ke...@et...> - 2003-07-21 00:45:27
|
I have released mknbi-1.4.1 at http://www.etherboot.org The main change in 1.4.1 is code by Robb Main to handle larger disks (> 2 heads) in DOS ramdisks. The rest are mostly bug fixes. Here is the change log: + Number segments in disnbi from 0 both in messages and in filenames. + Fix problem found by Eric in startmenu.S which affects segment override on 486s. + Add -I. to CFLAGS to make sure we get our includes instead of the system's. + In disnbi, call binmode on O not 0. + Quick and dirty Perl script to convert NBI Linux images to ELF. + Patches from Robb Main to handle larger "disks". + Added a --version option to display version. + Use lret to jump off to kernel instead of indirect jump through a data location. + Warn if in a .UTF-8 locale as this may affect binary string handling. MD5 sums: 0b17b4361f818e6a620ddd9f4cf8917b mknbi-1.4.1-1.noarch.rpm e4cf2df69753dfd8c4680f4ace15005c mknbi-1.4.1-1.src.rpm 631ea483ed429e369bc52e2f302a6b27 mknbi-1.4.1.tar.gz |
|
From: <ke...@et...> - 2003-07-20 12:37:31
|
>The developer manual is now uptodate with the current source. Not everything >is documented (for example not every file in src/core), but I think that >nothing is outdated anymore. >I also added src/util/get-pci-ids, a utility that I used to scan for new PCI >IDs in the Linux kernel source and that can be useful when anybody wants to >do this again. > >Georg Great, thanks very much. I'll have a look through it this week. |
|
From: Georg B. <gb...@us...> - 2003-07-20 12:26:37
|
The developer manual is now uptodate with the current source. Not everything is documented (for example not every file in src/core), but I think that nothing is outdated anymore. I also added src/util/get-pci-ids, a utility that I used to scan for new PCI IDs in the Linux kernel source and that can be useful when anybody wants to do this again. Georg |
|
From: <Gee...@xs...> - 2003-07-20 09:19:58
|
On Sat, Jul 19, 2003 at 03:44:27PM +0200, Geert Stappers wrote: > On Sat, Jul 19, 2003 at 11:07:36PM +1000, Ken Yap wrote: > > >While playing with the documentation I noticed that some entities like > > >_ appear literally in the output. I am using > > > > > >SGMLtools-Lite version 3.0.3 > > > > > >Is this a known problem, or do I need another version of sgmltools? > > > > I'm using sgmltools-lite 3.0.2. I see what you mean by the _ in > > the sgml files. This probably is due to no definition for this entity. > > The SGML files were created by automatic conversion of the ones on 5.0 > > so it's quite possible the process is not perfect. For example there are > > still some unclosed tags. Maybe _ should be called something > > else, &underscore;? Anybody know the official name of _? > > > > underscore > > > IIRC it not a resevered character in SGML/XML, > so you can s/_/_/. > Correcting myself: IIRC it is not a resevered character in XML, so you can s/_/_/ in XML files. Geert Stappers |