kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: victorascroft@gmail.com (victorascroft at gmail.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Best approach to explore the linux source code
Date: Sat, 15 Aug 2015 22:47:40 +0530	[thread overview]
Message-ID: <20150815171740.GA13388@Sanchayan-Arch> (raw)
In-Reply-To: <CABSox7gWiy+qcUn9BfDpFonAhD2CfNN9YYOzaQiEDWJq4LBL3w@mail.gmail.com>

On 15-08-15 12:28:06, Umair Khan wrote:
> Hi everyone,
> 
> I'm a final year undergraduate student. I've been spending a lot of
> time with OS books these days.
> I've been reading about the internals of the Linux kernel and drivers
> in the books. But, I've never really seen them in action except the
> drivers. Hacking a driver is easy.

Hacking a driver is easy? :)

> 
> Is there any good approach/tutorial to walk me through the source code
> of the kernel ?

There is only one approach to understanding any code. Reading the code
and understanding how different things interact. If you have doubts
you can always ask here.

Read Linux Device Drivers? Though that will still not prepare you
for actual code. Eudyptula Challenge?

> 
> Also, I'm using a self built linux kernel 4.2 on my laptop. Is there
> any way that I can contribute upstream to the kernel. I'm using 4.2 in
> the hope to find bugs in driver stuffs. I haven't found any yet.

http://lxr.free-electrons.com/source/Documentation/SubmittingDrivers
http://lxr.free-electrons.com/source/Documentation/SubmittingPatches

Just running the kernel might not always point out bugs.

  reply	other threads:[~2015-08-15 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15  6:58 Best approach to explore the linux source code Umair Khan
2015-08-15 17:17 ` victorascroft at gmail.com [this message]
2015-08-16  1:15   ` Kenneth Adam Miller

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=20150815171740.GA13388@Sanchayan-Arch \
    --to=victorascroft@gmail.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).