Writing device drivers
Hi all,
I've followed up LDD3 and started off with writing device drivers . As usual i've started with char drivers given in that book and also started to make minor modifications to learn it better and so on.
Now i would like to know how to take it forward and start writing drivers for a profession.
I know its too early to call myself a guy writing device drivers but how do i take if forward from here so that i can become one.
Is the only solution to pick up a device which does not work on linux and get it working? Are there any other ways as well?
Shampavman
On Wed, Jun 12, 2013 at 8:11 AM, shampavman <[email protected]> wrote:
Hi all,
I've followed up LDD3 and started off with writing device drivers . As usual i've started with char drivers given in that book and also started to make minor modifications to learn it better and so on.
Now i would like to know how to take it forward and start writing drivers for a profession.
I know its too early to call myself a guy writing device drivers but how do i take if forward from here so that i can become one.
Is the only solution to pick up a device which does not work on linux and get it working? Are there any other ways as well?
Shampavman
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Shampavman
There are many ways to became a Linux Device Driver Developer.
-> New Embedded platforms ; There are many platforms with none official Linux kernels ( came to my mind some with HDMI like DN2800MT) -> Fix and test the current development kernel. Check on Bugzilla the thousands of bugs that haven't been fixed ( waiting for you )
Hope it helps
Regards
Victor Rodriguez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130612/8fa1067c/attachment.html
Quoted 28 lines · Victor Rodriguez
On Wed, Jun 12, 2013 at 8:11 AM, shampavman <[email protected] <mailto:[email protected]>> wrote:
Hi all,I've followed up LDD3 and started off with writing device drivers . As usual i've started with char drivers given in that book and also started to make minor modifications to learn it better and so on.
Now i would like to know how to take it forward and start writing drivers for a profession.
I know its too early to call myself a guy writing device drivers but how do i take if forward from here so that i can become one.Is the only solution to pick up a device which does not work on linux and get it working? Are there any other ways as well?
Shampavman
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org <mailto:[email protected]>
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Quoted 6 lines
Hi Shampavman
There are many ways to became a Linux Device Driver Developer.
-> New Embedded platforms ; There are many platforms with none official Linux kernels ( came to my mind some with HDMI like DN2800MT)
I had to state my other problem here. Without actual hardware to work on its not possible to do much right.
In such a scenario what can i do?
Quoted 3 lines
-> Fix and test the current development kernel. Check on Bugzilla the thousands of bugs that haven't been fixed ( waiting for you )
here again the same thing, Unless I have the right hardware i dont know what the heck works and what doesn't . Or is there another way to work around this limitation?
Quoted 6 lines
Hope it helps
Regards
Victor Rodriguez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130612/acd36178/attachment-0001.html
Quoted 2 lines · shampavman
Quoted 2 lines
Now i would like to know how to take it forward and start writing drivers for a profession.
<snip>
Quoted 3 lines
here again the same thing, Unless I have the right hardware i dont know what the heck works and what doesn't . Or is there another way to work around this limitation?
Why not look for a problem with an existing device driver you *can* test? I can think of several annoying bugs that my laptop has had at different times. Even if you can't make contributions right away, just looking at the code of an interesting driver can help your skill & understanding. Probably more so than trying to write one from scratch, because you get the benefit of others' experience.
Regards,
Jonathan Paugh