[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Intel PRO/100 M Mobile Connection
From: |
Hans-Peter Jansen |
Subject: |
Re: Intel PRO/100 M Mobile Connection |
Date: |
Mon, 18 Aug 2003 17:17:48 +0200 |
User-agent: |
KMail/1.5.1 |
Hi Brenda,
On Monday 18 August 2003 01:44, Brenda wrote:
>
[...]
>
> Probing...[EEPRO100]No ethernet card found.
>
> It turns out (according to Windows XP, which is what is running on
> the tablet right now), the tablet has an "Intel(R) PRO/100 M Mobile
> Connection" Ethernet adapter. However, the driver for this adapter
> was added to eepro100.c in etherboot after version 5.0.5, when grub
> last snagged it.
>
> etherboot seems to have changed quite a bit (and added a lot of
> driver support) since then; using what is in etherboot now, I could
> figure out how to get my particular Ethernet adapter working and
> supply you with a patch for grub, but I wondered whether there might
> be an effort to get synced up with all of etherboot sometime soon?
> Also, are there any licensing reasons I should not copy code from the
> current etherboot? (And, I'm curious -- why are grub and etherboot
> separate projects? They seem pretty similar at first glance.)
Well, they're different projects with different development strategies.
As you found out, the etherboot drivers as adopted in grub are
hopelessly behind.
I'm a heavy diskless user, so I started with my primary concern:
booting netboot tagged images via grub. A first inquiry here gave no
result. So I made up support for the tagged image support myself,
adopted a more current e1000 driver, announced it to the list, but that
doesn't gave _any_ feedback, either.
This leaves me in the impression, nobody with interest in this topic is
listening in this ML 8-|, and I stopped posting here to not increase
my troll count. You we're much luckier, since you triggered the right
keywords [*BSD] to get an answer from a maintainer in spe, if I
followed this list correctly.
BTW: I started adapting the infrastructure for eb 5.2, but haven't
solved the problem of controlling the linker in the way, eb does.
This would make integrating a new eb driver adding a few lines to
configure.in and netboot/Makefile.in. I'm not sure, if the relocation
tricks, eb uses, are applicable, either. The rest should be more or
less straight forward.
Getting absolutely no response doesn't actually incite me in this
effort, though.
Cheers,
Pete