[SOLVED] How to setup CONFIG_USB_DEVICE_CLASS & CONFIG_WO_BUS_DIRS in the Kernel?
Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How to setup CONFIG_USB_DEVICE_CLASS & CONFIG_WO_BUS_DIRS in the Kernel?
hello,
I could not change that parameter in kernel 3.8.11 because it seems not to be recognized in "make menuconfig". Do you know how to change it? Is it perhaps a bug?
If somebody know how to change this in menuconfig, I would be happy to know it.
I need a change of that parameter because..: http://www.libusb.org/ticket/119
that's not a bug, the CONFIG_USB_DEVICE_CLASS option has been removed from the kernel after it had been deprecated for many years. (See https://lkml.org/lkml/2012/4/25/444.) What board are you working with? Isn't it possible to use a new and mainstream method of managing USB devices such as udev?
that's not a bug, the CONFIG_USB_DEVICE_CLASS option has been removed from the kernel after it had been deprecated for many years. (See https://lkml.org/lkml/2012/4/25/444.) What board are you working with? Isn't it possible to use a new and mainstream method of managing USB devices such as udev?
The board: I dont have the description; this is a specific embedded hardware for civil use and no public board name is defined (not mainstream available for few euros at standard shops on the street; the hardware cost is between 13000 and 25000 euros depending of the version).
udev: the responsible for the architecture said "NO WAY" because he seems to have issues with udev at another place (dont ask which one).
Last edited by floppy_stuttgart; 08-18-2013 at 02:49 AM.
My target did not work. I had to deal with the non working libusb.
I wanted a working libusb because I wanted to use usb_modeswitch.
I just bought a huawei E220 which dont need usb_modeswitch and dont need a working libusb.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.