|
From: Eric W B. <ebi...@ln...> - 2002-07-26 05:55:08
|
ollie lho <ol...@si...> writes:
> On Fri, 2002-07-26 at 12:57, Eric W Biederman wrote:
> > >
> > > Not yet, but I can send you .tgz. I am consider committing patches
> > > to etherboot project in near future.
> >
> > We should probably sync up then, because I am in a similiar process.
> > Though I have still not been convinced that we need filesystem code...
> >
>
> I am about to ask you on this. I am not familiar with Etherboot guys
> and how should I reform my code. Features in my version:
First step. Subscribe to the etherboot-developers list, I am taking the
conversation there now.
> 1. SiSFb Lite support, with stupid vga console code.
> 2. Filesystem code from grub, currently only FAT and EXT2
> were tested but other file system code could be imported
> from grub easily.
>
> There are various quick hack in both Etherboot original part and my
> own addition. One problem I have is that Etherboot has a flat src
> directory, it would be very ugly to put all my code in it.
>
> > Though it should be noted that working with different drives and
> > different controlles seems to give some noticeably different results
> > so even after the code looks solid to everyone we need to keep our
> > eyes peeled for a while.
> >
>
> I think a proper controller driver and Identify/Set feature sequence
> is necessary to to cope with various IDE drives.
In this case all I have identified so far is the need for proper error
checking :) But we will see.
Let me summarize for you what changes I have been making to support
LinuxBIOS better, in etherboot. And we can figure out where to work
your stuff in from there.
Currently I have cvs access, and etherboot has a cvs development
branch open on sourceforge that I have been pushing my changes into
when the look like the will work. I don't intend to stop until
everything works again but there has been a little bit of breakage.
1) I have added relocation code so that etherboot now will relocate
itself to the top of memory after it has loaded, and I have done
most of the surgery so this works with normal etherboot as well.
With the relocation code in place we are free to expand the code
size of etherboot to > 64K.
2) I have ported the compressor to 32bit code allowing the LinuxBIOS
etherboot romimage to be self uncompressing.
3) I have done most of the work so that the etherboot drives will now
use virt_to_bus, bus_to_virt && ioremap allowing them to be
portable.
4) I have discussed on the mailing list and have gotten some approval
on how to do disk support when configuration via DHCP is in
control. Basically: ``filename "file::///disk0"'' or if we have a
filesystem, "file:///disk0/{partion number}/{filesystem path}
5) I have incorporated your windows ce loader into etherboot, though
it isn't as clean as it might be.
As for menuing and how to be more interactive with users as your code
does I'm not certain. But take each each issue up on the list and I
am fairly certain we can work something out.
Eric
|
