From: prasadjoshi124@gmail.com (Prasad Joshi)
To: kernelnewbies@lists.kernelnewbies.org
Subject: i/o opening error for PCI access
Date: Sun, 3 Apr 2011 23:47:41 +0100 [thread overview]
Message-ID: <BANLkTikwP8h0ny9pkBpXZQ51K74-H_t1Yw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikPRMOXm9BrZfpBcek_NiZe+fYwXQ@mail.gmail.com>
On Sun, Apr 3, 2011 at 6:11 PM, Sengottuvelan S
<sengottuvelan.s@gmail.com> wrote:
> Hi All,
>
> I am trying to access /dev/mem in my user process. I could not access
> because not a privileged access. I tried to use iopl(3) call in linux 2.6,
I am not sure, but after reading the manpage, it looks like iopl will
give access to the IO ports not the files.
> but i am getting unresolved symbol for this.? Is any other way to get access
> in user process. I am not sure how to solve this. Can you someone throw some
> light on this.
>
> ?? if(iopl(3)){
> ??????? fprintf(stderr, "Cannot get I/O permissions (being root helps)");
> ??????? return -1;
> ??? }
> ? if ((fd = open("/dev/mem", O_RDWR | O_SYNC)) < 0) {
> ??????? fprintf(stderr, "Failed to open /dev/mem");
> ??????? return -1;
> ??? }
If you look at the file permission, you will notice only root has
permission to write the /dev/mem
$ ls -l /dev/mem
crw-r----- 1 root kmem 1, 1 2011-04-03 08:42 /dev/mem
Opening it for read/write will surely fail.
Thanks and Regards,
Prasad
>
> --
> Regards,
> S. Sengottuvelan.
>
> --
> Regards,
> S. Sengottuvelan.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
next prev parent reply other threads:[~2011-04-03 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 17:11 i/o opening error for PCI access Sengottuvelan S
2011-04-03 22:47 ` Prasad Joshi [this message]
2011-04-04 0:19 ` Sengottuvelan S
2011-04-04 6:25 ` Mulyadi Santosa
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=BANLkTikwP8h0ny9pkBpXZQ51K74-H_t1Yw@mail.gmail.com \
--to=prasadjoshi124@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).