The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: chd_1@nktelco.net (C. H. Dickman)
Subject: [pups] Major/minor device numbers and device names for MSCP drives?
Date: Mon, 19 Jun 2006 17:43:33 -0400	[thread overview]
Message-ID: <44971A85.8060406@nktelco.net> (raw)
In-Reply-To: <00a601c6934e$b1e90b50$0401010a@GIZMO>

Robert Armstrong wrote:
>   Probably this is documented somewhere, but I really need a pointer 
> or a brief tutorial on the major/minor device numbers for mknod() and 
> the device names for MSCP drives in 2.11bsd.
This is what I remember about it all when I struggled with it a couple 
of years ago.

The 8 bit minor number has 3 parts: the upper two bits are the 
controller (4 controllers max), the middle 3 bits are unit number (8 
drives per controller) and the lower 3 bits are the partition (a-h).

The assignment of device names is static (or nearly static). The 
discovery code for the controllers checks them in the order listed in 
/dev/dtab and assigns a controller number to each that is discovered and 
in that order (the nearly static part). Note also that DEC has a 
standard order for controller addresses too (which might be different). 
After that, drives are accessed using the 3 bit unit number which MUST 
correspond to the MSCP unit number (a catch follows because of this). 
Partitions are accessed with the 3 bit partition number.

The catch is that MSCP unit numbers are supposed to be global cross all 
controllers and the microPDP-11/83 boot code assumes this. The boot code 
can only see the first unit n that is encountered and 2.11BSD can only 
see the drives with MSCP unit numbers less than 8.

If you only have one controller there is no problem. When you add 
multiple controllers, things get more complex because you can only boot 
the first 8 MSCP units if you want to be able to access them from 2.11BSD.

-chuck






 



  parent reply	other threads:[~2006-06-19 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  3:15 Robert Armstrong
2006-06-19  6:57 ` Jochen Kunz
2006-06-19 14:51   ` Robert Armstrong
2006-06-19 15:08 ` Johnny Billquist
2006-06-19 21:43 ` C. H. Dickman [this message]
2006-06-20 15:45   ` Robert Armstrong
2006-06-19 21:53 ` C. H. Dickman

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=44971A85.8060406@nktelco.net \
    --to=chd_1@nktelco.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).