In etherboot the things are already fix. In a trial-hack-grub tree I
used
for my experiments, I already dose the merger of the etherboot driver
eepro100.c into the GRUB tree.
This leads me to the question, how we will treat the GRUB 'netboot' tree
in sync with etherboot. One idea was to have real a separate tree for
the
driver files, so that they can be quite copied in. What will be the
strategy for that ?
With friendly regards
Christoph P.
OKUJI Yoshinori wrote:
>
> From: HORIKAWA Kazunori <[EMAIL PROTECTED]>
> Subject: Patch for EtherExpressPro100
> Date: Tue, 27 Feb 2001 00:58:59 +0900
>
> > Reading EEPROM failed in new EtherExpressPro100 card.
> > This patch fixes it.
>
> Thanks for your contribution. But, since the device drivers are derived
> from Etherboot, I don't want to modify the code directly, if
> possible. So, could you contact Etherboot developers, so Etherboot
> works with your card? Once Etherboot is fixed, we can port the code to
> GRUB in a normal way.
>
> Regards,
> Okuji
>
> _______________________________________________
> Bug-grub mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/bug-grub
--
-------------------------------------------------------------------------
private: [EMAIL PROTECTED]
company: [EMAIL PROTECTED]
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
