From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: 7eggert@gmx.de, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: man-pages-2.57 is released
Date: Mon, 18 Jun 2007 17:01:52 +0200 [thread overview]
Message-ID: <20070618150152.211030@gmx.net> (raw)
In-Reply-To: <E1I0HsK-0000of-5v@be1.lrz>
> Michael Kerrisk <mtk-manpages@gmx.net> wrote:
>
> > ./man2/ioperm.2
> > FIXME is the following ("Only the first 0x3ff I/O ports can be
> > specified in this manner") still true? Looking at changes in
> > include/asm-i386/processor.h between 2.4 and 2.6 suggests
> > that the limit is different in 2.6.
>
> You now have the full 64Kb port bitmap (8 KB).
> BTW1: linux/arch/i386/kernel/ioport.c still states having 8K of
> bitmaps to
> be excessive (and implicitely and now wrongly as not being done). Since
> there should only be few processes requiring iopl, the 8K should not be
> excessive. We need a native speaker to change this text, at least not me
> right now.
If someone can come up with a technical description of what
should should go in the man page, I'm happy to fix the English.
> CC Linus, because he admitted fiddeling with this file. (No MAINTAINER
> found)
>
>
> BTW2: My (possibly outdated) iopl manpage states that you'll need to be
> root
> change the iopl, but you only need CAP_SYS_RAWIO in order to increase the
> iopl.
The current page includes this text under ERRORS
EPERM The calling process has insufficient privilege to
call iopl(); the CAP_SYS_RAWIO capability is
required.
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages ,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
next prev parent reply other threads:[~2007-06-18 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8x3Cc-1LD-13@gated-at.bofh.it>
2007-06-18 14:06 ` man-pages-2.57 is released Bodo Eggert
2007-06-18 15:01 ` Michael Kerrisk [this message]
2007-06-18 18:00 ` H. Peter Anvin
2007-06-16 12:31 Michael Kerrisk
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=20070618150152.211030@gmx.net \
--to=mtk-manpages@gmx.net \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.