* Where to find up to date documentation
@ 2004-02-16 11:58 Mark Watts
2004-02-16 12:37 ` Niraj Kumar
2004-02-17 8:53 ` Yury V. Umanets
0 siblings, 2 replies; 3+ messages in thread
From: Mark Watts @ 2004-02-16 11:58 UTC (permalink / raw)
To: linux-kernel
-----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,
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-----
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Where to find up to date documentation
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
1 sibling, 0 replies; 3+ messages in thread
From: Niraj Kumar @ 2004-02-16 12:37 UTC (permalink / raw)
To: Mark Watts; +Cc: linux-kernel
Look at :
http://lwn.net/Articles/driver-porting/
Niraj
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,
>
>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/
>
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Where to find up to date documentation
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
1 sibling, 0 replies; 3+ messages in thread
From: Yury V. Umanets @ 2004-02-17 8:53 UTC (permalink / raw)
To: Mark Watts; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-02-17 8:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox