From: iamsasha01@yahoo.com (Sasha Mckinsey)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Next Steps After Char, Block, Serial & Parallel Drivers
Date: Tue, 11 Aug 2015 18:14:12 +0000 (UTC) [thread overview]
Message-ID: <826077833.2133788.1439316852261.JavaMail.yahoo@mail.yahoo.com> (raw)
Sending the email again as the previous message was unreadable due to rich text...apologies!
Hello,
Finally I can say I have completed learning the following (to a certain extent)
-C and Data structures
-Operating system concepts ( covered in my undergrad course)
-Linux kernel Development - Robert Love
-Linux Device Drivers - Partially (just finished Char, block, serial & parallel )
A book called "Essential Linux Device Drivers" - It looked rich a first look but I could go anywhere with it considering I didn't have the required Hardware. I have now cut my teeth into some bit of kernel but still I am not sure where to go from here. I know things but I am not happy or satisfied with what I now. I don't have the feel of a professional device driver programmer.
Here are my questions - two different questions and necessarily not connected to each other
What should be the next steps besides looking for a job. Getting a new hardware to write a driver I guess is not feasible all the time. Any ideas
During my Linux journey i realized Linux network stack development interests me alot but a friend of mine told me to stay away from it as its very vast and would consume me. Any ideas how should i approach it if I want to learn it from practical point of view. I am not looking for the names of books or resources I have all of them including the book understanding Linux network internals. I want to learn it from a practical point of view where in I can be actively involved unlike my status today in the world of device drivers.
Thanks!
reply other threads:[~2015-08-11 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=826077833.2133788.1439316852261.JavaMail.yahoo@mail.yahoo.com \
--to=iamsasha01@yahoo.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).