public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Need some help to understand the code
Date: Sat, 02 Apr 2016 08:15:47 +0200	[thread overview]
Message-ID: <2105035.hUCDNLol8h@sven-edge> (raw)
In-Reply-To: <1459513651.4076.17.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

On Friday 01 April 2016 14:27:31 Philipp Psurek wrote:
[...]
> If you have some spare time please recommend me some literature that
> has helped you on your way to write batman-adv code. I've two, three
> weeks to prepare myself and evaluate if I understand the code (or some
> parts of it) or participate in fixing some other Freifunk related
> issues.

Hm, I cannot speak for the other people but I would not know of any book which 
would prepare you perfectly for writing kernel code. The best resource is the 
kernel code itself (LXR is your friend to find things quickly) and the kernel 
documentation (e.g. in Documentation/*). Also the Linux Kernel Newbies [1] has 
some nice overviews and links to more information.

There are also some books which are well known and can help you to understand 
parts better [2,3,4,5]. But I think none of these are must-reads. Having some 
of them to find out more about a special topic can be helpful. But don't 
wonder when the example codes don't work anymore because the API in the kernel 
changed since the book was published :)

I don't know what tasks are currently open in the Freifunk GSoC. But if it is 
multicast related then you may better ask Linus about some more literature.

Kind regards,
	Sven

[1] http://kernelnewbies.org/
[2] http://www.kroah.com/lkn/
[3] http://www.oreilly.com/openbook/linuxdrive3/book/
[4] http://www.oreilly.com/catalog/understandlni/
[5] 
https://www.kernel.org/pub/linux/kernel/people/paulmck/perfbook/perfbook.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-04-02  6:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 12:27 [B.A.T.M.A.N.] Need some help to understand the code Philipp Psurek
2016-04-02  6:15 ` Sven Eckelmann [this message]
2016-04-02  7:57   ` Philipp Psurek
2016-04-04 23:15 ` Linus Lüssing
2016-04-05  7:11   ` Sven Eckelmann
2016-04-05  7:36     ` Hans-Werner Hilse

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=2105035.hUCDNLol8h@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.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