From a theoretical point of view anyone
can start with kernel driver development, so you can too. Practically speaking it requires lurking on the LKML, an inquisitive mindset, prior programming knowledge and a more than average amount of perseverance. I think the best way to start to see if you like it is to read kernel development books and see if you can do something with the examples, then move on to some "simple" driver.
Originally Posted by dahweeds
I have a tech support job. Tier 1 (..) Now my boss thinks that means I am the guy to take over the Linux kernel module development. (..) I am a 100% noooobie at kernel development. (..) The boss basically hands me a Linux kernel module book and says take over this Linux driver, on top of handling tier one tech support
...but (in my very subjective opinion)
all of this screams NO
to me. Not only in terms of difficulty
(dissecting proprietary protocols usually don't fare well, see for instance some utterly crappy SATA card implementations LKM developers have to fight with), job mismatch
(kernel development would be 3rd line support and should be paid like that), innocent misconceptions or deliberate slave-driving
(aka cost-saving) on your bosses part but also it should be obvious only the company will reap the benefits
, not you (except for you being able to say you did the development whilst working basically 2 jobs per day). I think it could do with some renegotiation...