From: Natanael Copa <natanael.copa@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] writing device drivers howto
Date: Tue, 22 Aug 2006 16:02:52 +0200 [thread overview]
Message-ID: <1156255372.17633.43.camel@localhost> (raw)
In-Reply-To: <OF862175CD.D4FCACAA-ONC12571D2.004A81C0-C12571D2.004ADC8D@cnsystems.at>
On Tue, 2006-08-22 at 15:37 +0200, andreas.sumper@cnsystems.at wrote:
>
> 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!
>
I don't have much experience with kernel development but I think you
need a device in /dev that you can control with ioctl to communicate
with the module.
I looked into how to access the md5/sha1/sha256 kernel modules and I
concluded that a /dev/crypto was needed. Someone had made a patch for it
but it doesn look like it will go into main kernel so I gave it up.
You can look how he did. google for cryptodev.
> Bye,
> Andy
--
Natanael Copa
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-22 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 13:37 [gentoo-embedded] writing device drivers howto andreas.sumper
2006-08-22 14:02 ` Natanael Copa [this message]
2006-08-22 14:48 ` Kelly Price
-- strict thread matches above, loose matches on Subject: below --
2006-08-22 13:54 Morgan, Austin D.
2006-08-22 18:50 ` Walter Goossens
2006-08-22 19:15 ` Vladimir Pouzanov
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=1156255372.17633.43.camel@localhost \
--to=natanael.copa@gmail.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