From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-ide@vger.kernel.org
Subject: Re: {linux-ide] ide errors redhat 9.0 install
Date: 07 Jun 2004 07:59:37 -0600 [thread overview]
Message-ID: <1086616777.3649.10.camel@patibmrh9> (raw)
> List: linux-ide
> Subject: {linux-ide] ide errors redhat 9.0 install
> From: "Paul Gimpelj" <pgi...()sym...>
> Date: 2004-06-04 3:59:37
> ...
> open source documentation on ... bus mastering ...
When I last googled in 2004-03, I found:
/* Design references include these Three sets:
*
* 1) ATAPI CDB's:
*
* bleeding edge: (mmc 5 not yet available)
* last stable: http://www.t10.org/ftp/t10/drafts/mmc4/mmc4r02g.pdf
* oldest original: http://www.bswd.com/sff8020i.pdf
*
* 2) ATAPI I/O:
*
* last stable: http://www.t13.org/docs2002/d1410r3b.pdf (ATA/PI 6.3b)
* oldest original: (again sff 8020i, see above)
*
* 3) PC I/O:
*
* http://developer.intel.com/design/chipsets/datashts/
* http://www.ctyme.com/intr/int.htm
* http://lxr.linux.no/source/include/linux/pci_ids.h
* http://www.google.com/search?q=intel+corporation+pci.exe+version+2.2
*
* Intel ICH5 25251601.pdf
*
* "Undocumented PC"
* http://www.amazon.com/exec/obidos/ASIN/0201622777
*
* "Chapter 7" "Interrupt Vector Table"
* esp. IRQ 2 9 14 15
*
* "Chapter 17" "Interrupt Control and NMI"
*
* "PCI System Architecture", Third Edition, 1995 MindShare
* http://www.amazon.com/exec/obidos/ASIN/0201409933
* http://www.amazon.com/exec/obidos/ASIN/0201309742
*
* !!FIXME: Find doc to say PIC IRR falls when INTRQ falls.
*/
Pat LaVarre
next reply other threads:[~2004-06-07 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 13:59 Pat LaVarre [this message]
2004-06-11 19:32 ` {linux-ide] ide errors redhat 9.0 install Paul Gimpelj
2004-06-13 15:55 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 4:02 Paul Gimpelj
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=1086616777.3649.10.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=linux-ide@vger.kernel.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