summaryrefslogtreecommitdiffstats
path: root/Documentation/digiboard.txt
diff options
context:
space:
mode:
authorRalf Baechle <ralf@linux-mips.org>1998-03-17 22:05:47 +0000
committerRalf Baechle <ralf@linux-mips.org>1998-03-17 22:05:47 +0000
commit27cfca1ec98e91261b1a5355d10a8996464b63af (patch)
tree8e895a53e372fa682b4c0a585b9377d67ed70d0e /Documentation/digiboard.txt
parent6a76fb7214c477ccf6582bd79c5b4ccc4f9c41b1 (diff)
Look Ma' what I found on my harddisk ...
o New faster syscalls for 2.1.x, too o Upgrade to 2.1.89. Don't try to run this. It's flaky as hell. But feel free to debug ...
Diffstat (limited to 'Documentation/digiboard.txt')
-rw-r--r--Documentation/digiboard.txt32
1 files changed, 32 insertions, 0 deletions
diff --git a/Documentation/digiboard.txt b/Documentation/digiboard.txt
index 0a49a427f..ab1490ada 100644
--- a/Documentation/digiboard.txt
+++ b/Documentation/digiboard.txt
@@ -254,3 +254,35 @@ sh /dev/MAKEDEV digi
;;
par[0-2])
----- End Makedev patch
+
+-----------------------------------------------------------------------------
+
+Changes v1.5.5:
+
+The ability to use the kernel's command line to pass in the configuration for
+boards. Using LILO's APPEND command, a string of comma separated identifiers
+or integers can be used. The 6 values in order are:
+
+ Enable/Disable this card,
+ Type of card: PC/Xi(0), PC/Xe(1), PC/Xeve(2), PC/Xem(3)
+ Enable/Disable alternate pin arrangement,
+ Number of ports on this card,
+ I/O Port where card is configured (in HEX if using string identifiers),
+ Base of memory window (in HEX if using string identifiers),
+
+Samples:
+ append="digi=E,PC/Xi,D,16,200,D0000"
+ append="digi=1,0,0,16,512,(whatever D0000 is in base 10 :)
+
+Driver's minor device numbers are conserved. This means that instead of
+each board getting a block of 16 minors pre-assigned, it gets however
+many it should, with the next card following directly behind it. A
+system with 4 2-port PC/Xi boards will use minor numbers 0-7.
+This conserves some memory, and removes a few hard coded constants.
+
+NOTE!! NOTE!! NOTE!!
+The definition of PC/Xem as a valid board type is the BEGINNING of support
+for this device. The driver does not currently recognise the board, nor
+does it want to initialize it. At least not the EISA version.
+
+Mike McLagan <mike.mclagan@linux.org> 5, April 1996.