From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Stefan Schoenleitner <dev.c0debabe@gmail.com>
Cc: linux-embedded@vger.kernel.org
Subject: Re: AT91 kernel programming documentation ?
Date: Wed, 30 Jul 2008 16:01:14 +0200 [thread overview]
Message-ID: <20080730140113.GY8254@pengutronix.de> (raw)
In-Reply-To: <4890724F.2020505@gmail.com>
On Wed, Jul 30, 2008 at 03:53:19PM +0200, Stefan Schoenleitner wrote:
> I'm looking for some good documentation concerning AT91 Linux kernel
> development. Currently I have a Olimex AT91SAM9260 development board
> which is supported by the at91 patch set.
The base functionality is supported in the Linux mainline.
> Now I would like to add different hardware to the board and write some
> kernel code for it.
What kind of hardware?
> Unfortunately, there doesn't seem to be a lot of documentation. At
> the moment I'm reading mach-at91 related source code and trying to
> find out how things work.
I assume you've already bought a copy of the Rubini Device Driver book?
> Specificly, I would like to know how the different SoC devices can be
> accessed and used, how I can do port multiplexing, how I can tell the
> kernel which hardware is attached to where and so on.
Check arch/arm/mach-at91/*. It very much depends on what you want to do.
Documentation/drivermodel/ might also be worth a look.
rsc
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
next prev parent reply other threads:[~2008-07-30 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 13:53 AT91 kernel programming documentation ? Stefan Schoenleitner
2008-07-30 14:01 ` Robert Schwebel [this message]
2008-08-01 6:36 ` Stefan Schoenleitner
2008-08-01 8:42 ` Book about embedded-type device drivers Thomas Petazzoni
2008-08-01 9:13 ` Markus Franke
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=20080730140113.GY8254@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=dev.c0debabe@gmail.com \
--cc=linux-embedded@vger.kernel.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).