lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Mon, 5 Nov 2012 23:57:50 +0600
From:	Muhammad Minhazul Haque <mdminhazulhaque@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: About Beceem WiMAX Module

Helo LKML,

I have an issue with a module named "bcm_wimax". This is a staging
module located at linux/drivers/staging/bcm. The problem is that, the
supported devices listed in the module are not all valid or there are
more to be added.

"modinfo bcm_wimax" returns the supported product and vendor ids.

...
alias:          usb:v19D2p0007d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0489pE017d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v19D2p0132d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v198FpBCCDd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v198Fp0220d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v198Fp0210d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v198Fp0300d*dc*dsc*dp*ic*isc*ip*
...

Here the product id 198f:bccd is obsolete cause it is a storage device
to load device driver which uses module "usb_storage". There are more
devices with id 19d2:0172, 19d2:0173 and so on. They all have
"beceXXXX" chip inside and the module "bcm_wimax" works fine with
them. The only problem is, custom modules are to be build before using
them and remove the original one. It would be great if more device id
is added and remove which are rarely used. I often get emails from
people using Virgin Mobile U760, Franklin Wireless u600 etc which have
another device ids.

I did a commit on Sir Linus's repo at
https://github.com/torvalds/linux/blob/master/drivers/staging/bcm/InterfaceInit.h.

At line 14, the following text

#define BCM_USB_PRODUCT_ID_226 0x0132 /* not sure if this is valid */

was changed to

#define BCM_USB_PRODUCT_ID_226 0x0173 /* ZTE AX326 */

Shouldn't this be approved?

I have devices with id 19d2:0172, 19d2:0173, 198f:015e also. So if any
help will be provided if anyone is interested. Feel free to ask any
question regarding this device/module/api.

Thank you.

--
MD: Minhazul Haque,
CSE 10, RUET, Rajshahi
about.me/mdminhazulhaque
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ