Hello,

I am from an embedded background with a good experience, in an entry level driver development. i.e. I did read & practice the driver development & advanced Linux programming textbooks & tutorials (such as: http://free-electrons.com/doc/traini...nel-slides.pdf). Further, I joined mailing lists to learn more & develop.

BUT: mailing lists look unorganized & many of its posts (if not all) are about a developer who found not-needed code line, added a set of comments, or added a missed empty else{} after an if{}. That is NOT what I am looking for. I am looking for developing a driver from scratch, or a reported driver bug that I would test & solve. So, HOW TO DO THIS?

Another important question is related to the rest of the posts: there are no documentation for the code. Therefore, the code is very hard to understand. In that case a code may look like the following driver
http://lxr.linux.no/#linux+v3.19.1/d...oth/hci_vhci.c
http://lxr.linux.no/#linux+v3.19.1/d.../cdrom/cdrom.c

e.g. it has no comment which function does what! These given names, what do they mean!! … So, ANY RECOMMENDATIONS FOR HOW TO GET A CODE (LIKE THE GIVEN) UNDERSTANDABLE?

Thank you very much.

http://lwn.net/Kernel/LDD3/
gl

1 members found this post helpful.

1. Write your driver.
2. Put it in the correct place in the tree.
3. Create a proper git commit.
4. Prepare a patch with git format-patch.
5. Run ./scripts/get_maintainer.pl on your patch.
6. Send the patch using git send-email to addresses identified in step 5.

Good thing about such reviews is that if its really all reviewers found, once you fix those stylistic issues (which should be trivial), your patch has great chances of being accepted.

Linux kernel review process is the best I have encountered to date.

You might try Kernel Bug Tracker, but I personally never used it. If you want to try something smaller, you can create an account at Coverity, add Linux to your projects and look through defects Coverity identified.