From: "Morgan, Austin D." <AUSTIN.D.MORGAN@saic.com>
To: gentoo-embedded@lists.gentoo.org
Subject: RE: [gentoo-embedded] writing device drivers howto
Date: Tue, 22 Aug 2006 06:54:21 -0700 [thread overview]
Message-ID: <F23B2C80E3825F47B93655363249D0570C790A@0695-its-exmp01.us.saic.com> (raw)
The book Linux Device Drivers is my favorite reference for this type of
question. You can purchase it from anyone who has OReilly books, or
download it since it is published under Creative Commons. The newest
version is 3rd ed.
Austin Morgan
-----Original Message-----
From: gentoo-embedded+bounces-1145-AUSTIN.D.MORGAN=saic.com@gentoo.org on
behalf of andreas.sumper@cnsystems.at
Sent: Tue 8/22/2006 8:37 AM
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] writing device drivers howto
Hi list!
This is some sort of offtopic, but I guess this is the best point to ask.
I have an embedded system running linux. I need to access some special
registers (e.g. containing the clock cycles, ...) So I managed to write a
very simple module, which is able to access the registers. But what makes
me worrying now, is the way, I have to get the data into my user-space
application. Is there some documentation, concerning writing device
drivers and accessing them from the user space anywhere? I found some
documentation, but either I did not understand the part about getting data
from kernel space into user space, or it was just simply missing.
Maybe anyone here can help me out!
Thanks in advance and kind regards!
Bye,
Andy
--
gentoo-embedded@gentoo.org mailing list
next reply other threads:[~2006-08-22 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 13:54 Morgan, Austin D. [this message]
2006-08-22 18:50 ` [gentoo-embedded] writing device drivers howto Walter Goossens
2006-08-22 19:15 ` Vladimir Pouzanov
2006-08-23 7:22 ` andreas.sumper
-- strict thread matches above, loose matches on Subject: below --
2006-08-22 13:37 andreas.sumper
2006-08-22 14:02 ` Natanael Copa
2006-08-22 14:48 ` Kelly Price
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=F23B2C80E3825F47B93655363249D0570C790A@0695-its-exmp01.us.saic.com \
--to=austin.d.morgan@saic.com \
--cc=gentoo-embedded@lists.gentoo.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