From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ehci/uhci interrupts
Date: Sun, 4 May 2014 13:14:22 -0400 [thread overview]
Message-ID: <5f22673ec1d893b9923e44a177b8e79d@brasstown.quanstro.net> (raw)
In-Reply-To: <ad00635822fff872369f310379f008bd@proxima.alt.za>
> > there are lots of small ways to improve things, too. i'd be happy
> > to talk about that on or off list. one thing that immediately springs
> > to mind is additions to charles' kernel man pages.
>
> The list is not very busy and, I hate to admit, somewhat remote from
> Bell Labs. As a result, I think there would be no serious objection
> to add pertinent traffic to it.
>
> Personally, kernel pages would be a god-send (but an update of Nemo's
> commentaries would be even more so) and I would like to add discussion
> on the various Plan 9 flavours and how their differences should be
> consolidated or, if necessary, properly set down as distinguishing
> features.
these are the current section 9 pages, largely written by charles.
they pertain to all kernels
allocb conf delay devattach dmainit error eve inb intrenable kbdputc
kproc lib lock malloc monmwait newchan panic parsecmd qio qlock
readnum ref seconds sleep splhi uartp8250 xalloc
these are the current section 9nix (an unfortuante distinction that is
hopefully temporary)
adr panic physalloc qmalloc vmap
the current man pages can be accessed via, e.g.
http://www.9atom.org/magic/man2html/9/allocb
- erik
prev parent reply other threads:[~2014-05-04 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 15:26 erik quanstrom
2014-05-02 18:34 ` erik quanstrom
2014-05-03 5:14 ` lucio
2014-05-03 9:42 ` tlaronde
2014-05-03 19:45 ` erik quanstrom
2014-05-04 5:12 ` lucio
2014-05-04 10:41 ` tlaronde
2014-05-04 19:29 ` erik quanstrom
2014-05-05 10:50 ` tlaronde
2014-05-04 17:14 ` erik quanstrom [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=5f22673ec1d893b9923e44a177b8e79d@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).