From: Luther Huffman lutherh@mail.infinet.com
Subject: Adding pcdist to CD-ROM file system?
Date: Sun, 10 Dec 1995 21:44:19 -0500 [thread overview]
Message-ID: <19951211024419.cKbUnRc7qAksoNIHXShQ1bE0lnzA1ivI9ry3dItF0Tk@z> (raw)
Aha! Thanks. I'd been wondering about why it was named atapi2. I was
expecting atapi1 or even atapi0.
> From: "jim mckie " <jmk@plan9.att.com>
> To: 9fans@cse.psu.edu
> Date: Sun, 10 Dec 1995 10:49:57 -0500
> Subject: re: Adding pcdist to CD-ROM file system?
> Reply-to: 9fans@cse.psu.edu
> The slave/master jumper may have been a factor. Early ATA 'standards' (for
> want of a better word) forbade a slave without a master. The later ones say
> it's possible but do not sanction it. The way the ATA driver currently looks
> for drives is to use the 'execute device diagnostics' command then look at the
> status for the master and then the slave. Because of problems with some
> controllers i found it not advisable to try look at the status of the slave if
> the master doesn't exist.
>
> The mapping between ATA controller number, port and drive number is fixed:
> primary port 0x3F0 drives 0, 1
> secondary port 0x1F0 drives 2, 3
> tertiary port 0x1E8 drives 4, 5
> quaternary port 0x168 drives 6, 7
> This means there can be 'holes' in the drive name space.
> Although it is part of the ATA driver, ATAPI drives are named differently
> to not confuse them with hard drives. For example, with one hard drive on
> the primary and a CD-ROM on the secondary the drives are named
> /dev/hd0disk
> /dev/atapi2disk
>
>
>
next reply other threads:[~1995-12-11 2:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-11 2:44 Luther [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-12-21 22:21 steve
1995-12-10 19:23 td
1995-12-10 15:49 jim
1995-12-09 20:34 jim
1995-12-09 17:01 Luther
1995-12-09 15:26 Luther
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=19951211024419.cKbUnRc7qAksoNIHXShQ1bE0lnzA1ivI9ry3dItF0Tk@z \
--to=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).