Subject: Re: Nubus card debugging
To: None <port-mac68k@netbsd.org>
From: Michael R. Zucca <mrz5149@acm.org>
List: port-mac68k
Date: 08/05/2002 22:43:30
Here's the table from page 159 and the preceeding paragraph on page 158 in
"Designing Cards and Drivers":

The ByteLanes field tells the computer which of the four NuBus byte lanes
to use when communicating with an expansion card's declaration ROM. NuBus
byte lanes are defined under "NuBus Bit and Byte Structure" in Chapter 7.
The value of ByteLanes is composed by setting a bit in the low nibble for
each byte lane used and then setting the high nibble to the low nybble's
complement. The location of the first bit set to 1 in the low nibble also
determines the address of the ByteLanes, and hence the starting address of
the format block. Table 8-2 shows all the possible ByteLabens values and
their corresponding format block starting addresses (where s is the slot
number). Notice that the ByteLanes byte always occupies the highest address
available in the byte lanes being used. The Slot Manager doesn't recognize
any ByteLanes values not shown in Table 8-2.

Table 8-2 Possible ByteLanes values

ByteLanes		ByteLanes		Address of
used		value		Bytelanes
----------------------------------------------------------
0		0xE1		0xFsFF FFFC
1		0xD2		0xFsFF FFFD
0,1		0xC3		0xFsFF FFFD
2		0xB4		0xFsFF FFFE
0,2		0xA5		0xFsFF FFFE
1,2		0x96		0xFsFF FFFE
0,1,2		0x87		0xFsFF FFFE
3		0x78		0xFsFF FFFF
0,3		0x69		0xFsFF FFFF
1,3		0x5A		0xFsFF FFFF
0,1,3		0x4B		0xFsFF FFFF
2,3		0x3C		0xFsFF FFFF
0,2,3		0x2D		0xFsFF FFFF
1,2,3		0x1E		0xFsFF FFFF
0,1,2,3		0x0F		0xFsFF FFFF


----------------------------------------------
 Michael Zucca - mrz5149@acm.org
----------------------------------------------
 "I'm too old to use Emacs." -- Rod MacDonald
----------------------------------------------