wimax/i2400m: cleanup initialization/destruction flow
authorInaky Perez-Gonzalez <inaky@linux.intel.com>
Thu, 17 Sep 2009 00:53:57 +0000 (17:53 -0700)
committerInaky Perez-Gonzalez <inaky@linux.intel.com>
Mon, 19 Oct 2009 06:56:06 +0000 (15:56 +0900)
commit8f90f3ee83dc54e182d6a7548727cbae4b523e6e
tree8a81fd0076562a5c6e30a652c63fa25343783dc6
parentac53aed9349242095a780f57ac0c995fb170c950
wimax/i2400m: cleanup initialization/destruction flow

Currently the i2400m driver was starting in a weird way: registering a
network device, setting the device up and then registering a WiMAX
device.

This is an historic artifact, and was causing issues, a some early
reports the device sends were getting lost by issue of the wimax_dev
not being registered.

Fix said situation by doing the wimax device registration in
i2400m_setup() after network device registration and before starting
thed device.

As well, removed spurious setting of the state to UNINITIALIZED;
i2400m.dev_start() does that already.

Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
drivers/net/wimax/i2400m/driver.c
drivers/net/wimax/i2400m/i2400m.h
drivers/net/wimax/i2400m/netdev.c