On Sun, Aug 3, 2014 at 11:01 PM, Nick Krause <xerofoify@xxxxxxxxx> wrote: > On Sun, Aug 3, 2014 at 4:50 AM, Jassi Brar <jassisinghbrar@xxxxxxxxx> wrote: >> On Sun, Aug 3, 2014 at 11:07 AM, Nick Krause <xerofoify@xxxxxxxxx> wrote: >>> Hey Guys, >>> I assume after my other fuck ups , you assume I can't do kernel work >>> and I understand. But if you want to give me a second case >>> and allow me to help out with the usb subsystem that would be great too. >>> >> Why do you need someone to 'allow' you to do something? If you find >> some bug or see some feature missing, feel free to send in the >> patches. Just don't expect them to be always accepted and be ready to >> take lessons gratefully. Before that you need to do your homework >> because a bunch of bad patches could dent the credibility just as good >> ones build it up. >> >> HTH, >> -Jassi > > Thanks Jassi, > I was just wondering where to start, that's all. > Usually people start by understanding the subsystem they are interested in. For ex, you may start by understanding how USB works, how Linux's USB stack is organised, try to trace the enumeration process and later flow of control (in the process learn about tracering and debugging techniques in kernel). You may not have written the code but you could still understand it well. If you want to work upstream, read linux/Documentation/ and mailing-lists live/archived ... esp mails from gods of relevant subsystem. People may not always have time to personally explain things to you again. If you use Linux USB enough most probably you'll come across some device that has issues with Linux or, even more likely, the Linux driver available for the device is against some old version of Linux which you may try to upgrade and _test_ and then submit a patch. I am sure there is some todo-list online as well. Of course all this assumes one has good grasp on basic programming and debugging techniques before starting out. Cheers, Jassi -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
