Lines Matching refs:the
2 Driver for the Intel Wireless Wimax Connection 2400m
6 This provides a driver for the Intel Wireless WiMAX Connection 2400m
13 * Intel i2400m Echo Peak or Baxter Peak; this includes the Intel
16 + Linux kernel development package for the target kernel; to
18 the kernel development package corresponding to the running
20 linux-VERSION, the development package is called
26 2.1. Compilation of the drivers included in the kernel
28 Configure the kernel; to enable the WiMAX drivers select Drivers >
32 If USB or SDIO are not enabled in the kernel configuration, the options
33 to build the i2400m USB or SDIO drivers will not show. Enable said
34 subsystems and go back to the WiMAX menu to enable the drivers.
38 2.2. Compilation of the drivers distributed as an standalone module
45 Once built you can load and unload using the provided load.sh script;
46 load.sh will load the modules, load.sh u will unload them.
48 To install in the default kernel directories (and enable auto loading
49 when the device is plugged):
55 directory or if you want to build for a kernel that is not the
56 currently running one, set KDIR to the right location:
62 3. Installing the firmware
67 It has to be installed in the target system:
72 it as normal, with the rpm (rpm -i FIRMWARE.rpm) or dpkg
74 * BUSTYPE will be usb or sdio, depending on the hardware you have.
81 driver for the Intel i2400m.
87 The i2400m kernel driver is broken up in two main parts: the bus
88 generic driver and the bus-specific drivers. The bus generic driver
89 forms the drivercore and contain no knowledge of the actual method we
90 use to connect to the device. The bus specific drivers are just the
91 glue to connect the bus-generic driver and the device. Currently only
97 interfaces with the device on using an interface provided by the
99 easily reuse the hardware-glue to write drivers for other OSes; note
100 the hardware glue part is written as a native Linux driver; no
101 abstraction layers are used, so to port to another OS, the Linux kernel
102 API calls should be replaced with the target OS's.
106 To load the driver, follow the instructions in the install section;
107 once the driver is loaded, plug in the device (unless it is permanently
108 plugged in). The driver will enumerate the device, upload the firmware
109 and output messages in the kernel log (dmesg, /var/log/messages or
116 At this point the device is ready to work.
118 Current versions require the Intel WiMAX Network Service in userspace
119 to make things work. See the network service's README for instructions
129 To make changes permanent, for example, for the i2400m module, you can
138 During kernel bootup (if the driver is linked in the kernel), specify
139 the following to the kernel command line:
146 parameter, once set, will take effect only when the device is
147 reinitialized by the driver (eg: following a reset or a reconnect).
151 The driver will register debugfs entries that allow the user to tweak
153 entries are placed, which correspond to the three blocks a i2400m WiMAX
155 * /sys/kernel/debug/wimax:DEVNAME/ for the generic WiMAX stack
157 * /sys/kernel/debug/wimax:DEVNAME/i2400m for the i2400m generic
159 * /sys/kernel/debug/wimax:DEVNAME/i2400m-usb (or -sdio) for the
167 The files named *dl_* indicate knobs for controlling the debug output
191 By reading the file you can obtain the current value of said debug
194 To increase the debug level of, for example, the i2400m's generic TX
200 what is printed and the available levels, check the source. The code
205 The i2400m/rx_stats and i2400m/tx_stats provide statistics about the
206 data reception/delivery from the device:
216 Thus, to find the average buffer size received, divide accumulated
219 To clear the statistics back to 0, write anything to the rx_stats file:
225 Note the packets this debug file refers to are not network packet, but
226 packets in the sense of the device-specific protocol for communication
227 to the host. See drivers/net/wimax/i2400m/tx.c.
231 To echo messages received from user space into the trace pipe that the
232 i2400m driver creates, set the debug file i2400m/trace_msg_from_user to
239 By writing a 0, a 1 or a 2 to the file
240 /sys/kernel/debug/wimax:wmx0/reset, the driver performs a warm (without
241 disconnecting from the bus), cold (disconnecting from the bus) or bus
242 (bus specific) reset on the device.
244 5.2.5. Asking the device to enter power saving mode
246 By writing any value to the /sys/kernel/debug/wimax:wmx0 file, the
253 If upon connecting the device, the following is output in the kernel
258 This means that the driver cannot locate the firmware file named
259 /lib/firmware/i2400m-fw-usb-1.2.sbcf. Check that the file is present in
260 the right location.