[SOLVED] What should I select as my expertise?

whjeon · 03-26-2018, 08:10 AM

Dear Mentors!

I want to become a kernel developer, even maintainer, so I'm studying really hard with C language and also kernel development.
But I was wondering what should I choose as my expertise.
I heard that it's recommended to choose device driver which I have now, but then I have to choose network/wifi/rtl8723 or other rtl drivers.

But I want to study more and eventually want to become other part's maintainer or developer.

What's your advice to me? 'Should I just start with network device drivers and improve my experience?' or 'wait and study until I can contribute to what I wanted?'

Thanks for reading my question, and please hope you can help me a lot!

Turbocapitalist · 03-26-2018, 08:13 AM

Quote:

Originally Posted by whjeon

But I want to study more and eventually want to become other part's maintainer or developer.

Which other part is more interesting than network, wifi, rtl8723 and other drivers?

BW-userx · 03-26-2018, 08:13 AM

start out as suggested, then just add to that knowledge as you become more accustom to the type of work you're doing. taking little bytes is easier to chew and swallow then byting off more than you can chew and trying to ingest it all at once.

byte = bite

the suggestion:
"recommended to choose device driver which I have now"

is, because you already have it, therefore you have something already that you can work with and on to get an understanding of that in which you need to learn in order to get it to do what you need it to do. Then by working on that you should eventually see how the methodology can transverse onto something else of a similar type when you start working one something else that is similar to that in which you've already learned how to code for.

whjeon · 03-26-2018, 08:36 AM

Quote:

Originally Posted by BW-userx

start out as suggested, then just add to that knowledge as you become more accustom to the type of work you're doing. taking little bytes is easier to chew and swallow then byting off more than you can chew and trying to ingest it all at once.

byte = bite

the suggestion:
"recommended to choose device driver which I have now"

is, because you already have it, therefore you have something already that you can work with and on to get an understanding of that in which you need to learn in order to get it to do what you need it to do. Then by working on that you should eventually see how the methodology can transverse onto something else of a similar type when you start working one something else that is similar to that in which you've already learned how to code for.

OK! I decided to start with wifi drivers. Thanks for your another suggestion!
Thanks for help me again!

BW-userx · 03-26-2018, 08:44 AM

coding is fun!

Cheers!

syg00 · 03-26-2018, 08:45 AM

Start here.
My only advice is to make sure you pick something you are really interested in. The kernel code is deep and complex - and the community not for the faint of heart.

whjeon · 03-26-2018, 08:47 AM

Quote:

Originally Posted by syg00

Start here.
My only advice is to make sure you pick something you are really interested in. The kernel code is deep and complex - and the community not for the faint of heart.

Thanks for your resources. I didn't know that awesome documentation. Thanks again.

chrism01 · 03-28-2018, 11:06 PM

This may also be useful http://www.linuxtopia.org/online_boo...nel_index.html