|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Sun, 15 Feb 1998 18:02:17 -0600 (CST) From: "Daniel M. Eischen" <deischen@iworks.InterWorks.org> To: U.Soni@cs.ucl.ac.uk Cc: linux-scsi@vger.rutgers.edu > Thinking about this (and taking clues from the source -luke :-) ), it > might be easier and safer to add a runtime option so that in the > infrequent case where termination needs to be forced, it can be > asserted on the command line -or via lilo. > > For example using the following; > > high_byte:[0,1] # Force high byte termination; 0 off, 1 on > low_byte:[0,1] # Force low byte termination; 0 off, 1 on Yes, that is a better idea and one that I'll look to include after I finish what I'm currently working on. I prefer using one identifier for termination though: term:[0,2,3] The LSbit (0) would be low byte termination, and the MSbit (1) would be high byte termination. As in: aic7xxx=term:0 # Low off, High off aic7xxx=term:2 # Low off, High on aic7xxx=term:3 # Low on, High on Anything else is obviously illegal. One could use hex numbers to make it more clear (even though it doesn't really ;-): aic7xxx=term:0x2 If you do this, make the variable (let's call it aic7xxx_termination) it is stored in have a default value of -1 to indicate using settings stored in BIOS. This also brings up the subject of what to do for multiple controllers. Perhaps we could add another option for specifying the HBA (by order probed in the aic7xxx driver). Then you could do: aic7xxx=hba:0,term:2,hba:1,extended,hba:2,term:3 This would set termination to Low off, High On for the first controller found, extended translation on for the second controller found, and termination to Low on, High off for the third controller found. Failing to specify an HBA on the command line would probably mean you'd want a global setting since that's what it does now. We wouldn't want to only apply settings to the first controller in this case because it might break for others who upgrade and don't know about the change. Dan Eischen deischen@iworks.InterWorks.org
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |