From: "John Zhou" <zjzhou@newrocktech.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: how to read/write registers of CPU or Device from user space
Date: Mon, 12 Jan 2004 10:20:10 +0800 [thread overview]
Message-ID: <000001c3d8b2$9b18add0$b702a8c0@newrock2> (raw)
In-Reply-To: <367D9728-436D-11D8-A844-000393911DE2@sara.nl>
Hi, all,
when debugging kernel or driver, we need to read/write registers of CPU and devices. I wanna use /dev/mem to do, is it possible? if need to do others things? is it better to write a driver for read/write CPU/device's registers by myself?
Do you have any good advice?
Thanks in advance!
John
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-12 2:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 17:33 Linux on IBM 9076 nodes Bill Noffsinger
2004-01-09 18:32 ` linas
2004-01-09 23:12 ` Remco Post
2004-01-10 0:37 ` Anton Blanchard
2004-01-10 13:02 ` Remco Post
2004-01-12 2:20 ` John Zhou [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 13:48 how to read/write registers of CPU or Device from user space Muhammad Sarwar
2004-01-12 15:31 ` Hollis Blanchard
2004-01-12 20:14 ` Hollis Blanchard
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='000001c3d8b2$9b18add0$b702a8c0@newrock2' \
--to=zjzhou@newrocktech.com \
--cc=linuxppc-dev@lists.linuxppc.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).