2004-01-06 23:51:47

by Sergio Vergata

[permalink] [raw]
Subject: Kconfig entryf or Pegasus USB Ethernet device

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

Just a small hint for USB Ethernet device.

I only have 1000Mbit card and for testing purpose an External USB
Ethernetdongle, so why should I build Ethernet 10 /100 Mbit when i only need
an USB Network adapter.

So if I'm right this should work too just like the other devices too.

CU Sergio

- --- Kconfig.old 2004-01-06 21:26:37.000000000 +0100
+++ Kconfig 2004-01-06 21:35:53.000000000 +0100
@@ -69,7 +69,7 @@

config USB_PEGASUS
tristate "USB Pegasus/Pegasus-II based ethernet device support"
- - depends on USB && NET_ETHERNET
+ depends on USB && NET
select MII
---help---
Say Y here if you know you have Pegasus or Pegasus-II based adapter.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQE/+0oKVP5w5vF/2y8RAoaaAKCauI7Atzrkc6HpxUXM77YZeE9UGwCg7JKF
VYTBCKqlhFPtDsOhflbh54s=
=M0Jf
-----END PGP SIGNATURE-----


2004-01-07 00:28:37

by David Hollis

[permalink] [raw]
Subject: Re: Kconfig entryf or Pegasus USB Ethernet device

On Tue, 2004-01-06 at 18:51, Sergio Vergata wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> Just a small hint for USB Ethernet device.
>
> I only have 1000Mbit card and for testing purpose an External USB
> Ethernetdongle, so why should I build Ethernet 10 /100 Mbit when i only need
> an USB Network adapter.
>
> So if I'm right this should work too just like the other devices too.
>
The NET_ETHERNET config option is just for Kconfig and does not have an
impact on the resulting kernel. It does make more semantic sense to
have Pegasus, usbnet, etc use the NET_ETHERNET option as they are
Ethernet devices, not some type of generic network device.
Additionally, depending on how you configure usbnet, it will require MII
which also depends on NET_ETHERNET, so you would wind up that way
anyway.

--
David T Hollis <[email protected]>