On Wed, 2012-12-12 at 20:16 -0300, Silvio Quadri wrote:
> 2012/12/12 Silvio Quadri <[email protected]>:
> > 2012/12/12 Dan Williams <[email protected]>:
> >> On Wed, 2012-12-12 at 09:28 -0300, Silvio Quadri wrote:
> >>> 2012/12/12 <[email protected]>:
> >>> > On Tue, 11 Dec 2012 22:55:07 -0300
> >>> > Silvio Quadri <[email protected]> wrote:
> >>> >
> >>> >> Now, the device is detected on boot, but the message is the same ...
> >>> >> Complete dmesg at http://pastebin.com/hgf2fuXm
> >>> >> (usb errors at line 728)
> >>> >
> >>> >
> >>> > The following line suggests it's not just a matter of a missing device
> >>> > ID, but that the driver doesn't support your device:
> >>> >
> >>> > [ 12.960534] i2400m_usb 1-5:1.0: device boot: tried all the
> >>> > echo/acks, could not get device to respond; giving up
> >>> >
> >>> > It could just be a matter of adding the appropriate wakeup command for
> >>> > your device, but more likely other things will have to be tweaked as
> >>> > well for the device to function.
> >>> >
> >>> >
> >>> > Sorry,
> >>> >
> >>> > H7
> >>>
> >>> Hypnos, Dan, thanks for your help!
> >>> Maybe with reverse engineering I can wakeup the device? I'm not an
> >>> expert, but I'm reading Argentinian blogs and there are people trying
> >>> to make to work this device (120.000 childrens in metropolitan area
> >>> must boot in Win7 for connect to internet).
> >>
> >> Can you get access to the WiFi/WiMAX card itself and tell me the model
> >> number? Is it anything like "612BNXHMW", eg:
> >>
> >> http://i.ebayimg.com/t/INTEL-6150-WIRELESS-ADVANCED-N-WIMAX-HALF-MINI-HEIGHT-CARD-MINICARD-612BNXHMW-/00/s/MTIwMFgxNjAw/$(KGrHqZHJCIE8mU5sorBBPPbodBNRQ~~60_57.JPG
> >>
> >> Dan
> >>
> >
> > Maybe 612BNXHMWG ?
> > Tonight I can open one and take a picture.
> >
> >
>
> Picture at https://docs.google.com/open?id=0B2lbUb7QZtGpamV1OGY4VWRZZ1k
> The code is 612BNXHMW (without G) as you say.
Thanks; I just got my 6150 in the mail today, and it does work with the
existing drivers if you add the device IDs to the right places. I've
posted a patch to the kernel netdev mailing list, also attached here.
It worked for me.
Dan
diff --git a/drivers/net/wimax/i2400m/i2400m-usb.h b/drivers/net/wimax/i2400m/i2400m-usb.h
index 6650fde..9f1e947 100644
--- a/drivers/net/wimax/i2400m/i2400m-usb.h
+++ b/drivers/net/wimax/i2400m/i2400m-usb.h
@@ -152,6 +152,9 @@ enum {
/* Device IDs */
USB_DEVICE_ID_I6050 = 0x0186,
USB_DEVICE_ID_I6050_2 = 0x0188,
+ USB_DEVICE_ID_I6150 = 0x07d6,
+ USB_DEVICE_ID_I6150_2 = 0x07d7,
+ USB_DEVICE_ID_I6150_3 = 0x07d9,
USB_DEVICE_ID_I6250 = 0x0187,
};
diff --git a/drivers/net/wimax/i2400m/usb.c b/drivers/net/wimax/i2400m/usb.c
index 713d033..080f363 100644
--- a/drivers/net/wimax/i2400m/usb.c
+++ b/drivers/net/wimax/i2400m/usb.c
@@ -510,6 +510,9 @@ int i2400mu_probe(struct usb_interface *iface,
switch (id->idProduct) {
case USB_DEVICE_ID_I6050:
case USB_DEVICE_ID_I6050_2:
+ case USB_DEVICE_ID_I6150:
+ case USB_DEVICE_ID_I6150_2:
+ case USB_DEVICE_ID_I6150_3:
case USB_DEVICE_ID_I6250:
i2400mu->i6050 = 1;
break;
@@ -759,6 +762,9 @@ static
struct usb_device_id i2400mu_id_table[] = {
{ USB_DEVICE(0x8086, USB_DEVICE_ID_I6050) },
{ USB_DEVICE(0x8086, USB_DEVICE_ID_I6050_2) },
+ { USB_DEVICE(0x8087, USB_DEVICE_ID_I6150) },
+ { USB_DEVICE(0x8087, USB_DEVICE_ID_I6150_2) },
+ { USB_DEVICE(0x8087, USB_DEVICE_ID_I6150_3) },
{ USB_DEVICE(0x8086, USB_DEVICE_ID_I6250) },
{ USB_DEVICE(0x8086, 0x0181) },
{ USB_DEVICE(0x8086, 0x1403) },
_______________________________________________
wimax mailing list
[email protected]
http://lists.linuxwimax.org/listinfo/wimax
