From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org
Subject: Basic Structure of b43 wireless driver
Date: Wed, 23 May 2012 16:00:02 +0200 [thread overview]
Message-ID: <20120523160002.4d6ddc37@milhouse> (raw)
In-Reply-To: <CADMmn=uYYn__0vLOBGR3SGCvnWmqa3Yi+x4sRy_S-P2N382f8g@mail.gmail.com>
On Wed, 23 May 2012 09:38:33 +0700
Le Hoang Phuong <nhoxleesieuquay@gmail.com> wrote:
> "how I can read and understand these codes?").
The best way to read and understand code is to read it. Really. I think
this is the only way to get you started. Start in main.c and look through
the code. But first learn how linux device drivers work in general.
There are quite some books and tutorials on the net on this topic.
If you have any _specific_ question about parts of the code, we'll be happy
to answer them.
--
Greetings, Michael.
PGP encryption is encouraged / 908D8B0E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20120523/a88e2543/attachment.sig>
prev parent reply other threads:[~2012-05-23 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 2:38 Basic Structure of b43 wireless driver Le Hoang Phuong
2012-05-23 14:00 ` Michael Büsch [this message]
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=20120523160002.4d6ddc37@milhouse \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.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).