summaryrefslogtreecommitdiffstats
path: root/drivers/net/wimax/i2400m/fw.c
diff options
context:
space:
mode:
authorInaky Perez-Gonzalez <inaky@linux.intel.com>2008-12-20 16:57:45 -0800
committerGreg Kroah-Hartman <gregkh@suse.de>2009-01-07 10:00:18 -0800
commitce6cde92803e961d95ddacdf74bd8b067f82f7d4 (patch)
tree5bdbfa6448e0bb1d0795da8fa222b16ea2b2736c /drivers/net/wimax/i2400m/fw.c
parent024f7f31ed15c471f80408d8b5045497e27e1135 (diff)
downloadtalos-obmc-linux-ce6cde92803e961d95ddacdf74bd8b067f82f7d4.tar.gz
talos-obmc-linux-ce6cde92803e961d95ddacdf74bd8b067f82f7d4.zip
i2400m: linkage to the networking stack
Implementation of the glue to the network stack so the WiMAX device shows up as an Ethernet device. Initially we shot for implementing a Pure IP device -- however, the world seems to turn around Ethernet devices. Main issues were with the ISC DHCP client and servers (as they don't understand types other than Ethernet and Token Ring). We proceeded to register with IANA the PureIP hw type, so that DHCP requests could declare such. We also created patches to the main ISC DHCP versions to support it. However, until all that permeates into deployments, there is going to be a long time. So we moved back to wrap Ethernet frames around the PureIP device. At the time being this has overhead; we need to reallocate with space for an Ethernet header. The reason is the device-to-host protocol coalesces many network packets into a single message, so we can't introduce Ethernet headers without overwriting valid data from other packets. Coming-soon versions of the firmware have this issue solved. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/net/wimax/i2400m/fw.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud