Hi Inaky, > This code is broken up in a WiMAX subsystem and a driver for the Intel > 2400m Wireless WiMAX Link. To be able to fully utilize WiMAX services, > you need extra pieces of device-specific user space software; for now, > there is a C level API (the Common API) to use/control it, but a high > level API over DBUS that should work for any device is in the > works. See details further below. this is not a big deal, but a more general question on how the layout of the kernel source code tree. So the whole WiMAX subsystem should be in net/wimax/, but for the drivers I think using drivers/net/wimax/ is wrong. None of these drivers should ever register an Ethernet or network device directly. They register themselves with the WiMAX subystem. So I would propose to use drivers/wimax/ here. We do the same with Bluetooth. All the drivers are under drivers/bluetooth/, because they don't register any kind of network device. Jeff, what is your take on this. Shouldn't be drivers/net/ only contain drivers that actually use struct net_device somehow? Regards Marcel
