ollie lho <[EMAIL PROTECTED]> writes: > On Fri, 2002-06-21 at 12:12, Eric W. Biederman wrote: > > > > However. > > a) Multiple NIC support has already been implemented. > > From etherboot cvs do: > > make rtl8139--eepro100.ebi > > > > Hmm. how is this been done ?? Is there any kind of "virtual switch" or > just poll a table of supported NIC ??
Just a poll table of supported NICs. Currently you can only use one at a time, but that isn't a major problem. Being able to use multiple copies of etherboot at a time > I am also think about implementing a general purpose bootloader > from scratch. Unfortunately, I crashed my HD last week so I have > to redesign it all over again. Ouch! > BTW, Eric, is it possible for ELF Boot to have XIP capability ?? > For example, currently, Etherboot is copied from Flash to RAM > before executing. Can we make the .text section's VMA/LMA > to the address of Flash chip and mark it something like NOLOAD ?? Actually that should work. We might have to double check that we ignore unknown program segments but yes. > I got this problem because our in-house etherboot is getting > bigger and bigger, and Linux/WinCE have different concept about > "reserved memory". :) The other solution is to get etherboot out of the way. There has been some discussion about how to do that on the etherboot-developers list, but it hasn't been implemented yet. What kind of concept does WinCE have of reserved memory. My gut impression is to just have etherboot move itself to the top of memory, but if it gets to big, that may be an issue. For the systems I work with I have issues like: how do I make the full 4GB of ram plugged into this machine available to the kernel. So I really don't have a feel if consuming an extra 300k-400k at the top of memory would be a problem. I currently have a solution in memtest86 that allows for arbitrary relocation, by making the application a shared library. The problem is I can't remove the useless strings for all of the global variables, so it bloats this a little bit. It is still better than having two copies of the application like memtest86 did. Eric
