From: Zheng Lv <lv.zheng.2015@gmail.com>
To: Madhu K <madhu.sk89@gmail.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Understanding the wireless architecture
Date: Sun, 8 Oct 2017 01:20:21 +0800 [thread overview]
Message-ID: <20171007172021.GA6184@lvzheng-thinkpad> (raw)
In-Reply-To: <CAA2oCOnOMcQbh1bEyF5hZjfFGdsw7wWLh=y5rPO54OQnDgV5SQ@mail.gmail.com>
On Sat, Oct 07, 2017 at 09:23:04PM +0530, Madhu K wrote:
> I am kernel newbie, I wanted to learn linux wireless architecture and
> I want to write some wireless drivers. So please suggest me some
> tutorials or documents which will help me to understand the linux
> wireless device drivers architecture.
I am also newbie. Although I have no plan to learn wireless
architecture, I do think that Linux kernel (device driver module)
programming is not newbie-friendly.
In my opinion, LDD3 is somehow outdated. Wireless network is not
covered, while there is a full chapter covering parallel port, which is
hard for newbies to learn due to difficulty to buy appropriate hardware.
Moreover, many interfaces are updated. Semaphores have been replaced by
mutexes long ago. There are also advanced .{read|write}_iter functions
in file_operations which can replace {.read|.write}. I cannot understand
the read_iter_zero function in drivers/char/mem.c after I read LDD3.
I wish a better resource for newbies to learn driver programming, maybe
LDD4, maybe a more detailed book elsewhere.
Cheers
Zheng Lv
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2017-10-07 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 15:53 Understanding the wireless architecture Madhu K
2017-10-07 17:20 ` Zheng Lv [this message]
2017-10-08 13:12 ` Christos Gkekas
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=20171007172021.GA6184@lvzheng-thinkpad \
--to=lv.zheng.2015@gmail.com \
--cc=linux-newbie@vger.kernel.org \
--cc=madhu.sk89@gmail.com \
/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