public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yury V. Umanets" <umka@namesys.com>
To: Mark Watts <m.watts@eris.qinetiq.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where to find up to date documentation
Date: Tue, 17 Feb 2004 10:53:23 +0200	[thread overview]
Message-ID: <1077008003.3548.4.camel@firefly> (raw)
In-Reply-To: <200402161158.06060.m.watts@eris.qinetiq.com>

On Mon, 2004-02-16 at 13:58, Mark Watts wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> Can someone recommend the best place to look for documentation on writing a 
> device driver for the 2.6.x kernel? (Preferably something with a worked 
> example)
> 
> I'd prefer a hardcopy book, but I can only see ones for 2.4 driver 
> development.
> 
> Cheers,
> 
It depends on what driver type you are developing. Anyway, IMHO the best
way to see it is to read the sources in linux/drivers directory.
> Mark.
> 
> - -- 
> Mark Watts
> Senior Systems Engineer
> QinetiQ TIM
> St Andrews Road, Malvern
> GPG Public Key ID: 455420ED
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFAMLBOBn4EFUVUIO0RAkl6AJ0adGg7fyud/njfY2byccccmV2kcACeI+gP
> i57VzaimePPv+VQpzxZt+Zs=
> =NmkT
> -----END PGP SIGNATURE-----
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
-- 
umka


      parent reply	other threads:[~2004-02-17  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 11:58 Where to find up to date documentation Mark Watts
2004-02-16 12:37 ` Niraj Kumar
2004-02-17  8:53 ` Yury V. Umanets [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=1077008003.3548.4.camel@firefly \
    --to=umka@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.watts@eris.qinetiq.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