From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: i/o opening error for PCI access
Date: Mon, 4 Apr 2011 13:25:04 +0700 [thread overview]
Message-ID: <BANLkTinw=X2_E-SmO-ZxzoV_hFz4F=MPSg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=VkTTxJei_ypKfZgmev6Z01oJiSA@mail.gmail.com>
On Mon, Apr 4, 2011 at 07:19, Sengottuvelan S <sengottuvelan.s@gmail.com> wrote:
> Hi Prasad,
>
> question is:? anyother way to access like iopl(3) function?.
libcap?
http://www.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.4/capfaq-0.2.txt
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-04-04 6:25 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
2011-04-04 0:19 ` Sengottuvelan S
2011-04-04 6:25 ` Mulyadi Santosa [this message]
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='BANLkTinw=X2_E-SmO-ZxzoV_hFz4F=MPSg@mail.gmail.com' \
--to=mulyadi.santosa@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).