Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

choosing base addresses on NICs



     Hi,
     
     I've never been clear on the base address thing.  And I've spoken with 
     a few others who seemed equally uncertain.  So on all of our behalves, 
     I am posing the following questions.  Any insight would be greatly 
     appreciated:
     
     I have 2 3c509B NICs.  Each has 3 connectors TP, coax and a 9(?)PIN.  
     I need to use the DOS software to configure these to use TP.  No 
     problem.  But I want to put them both in the same box (for the usual 
     reason).  So I have to consider IRQ and Base address (I can find the 
     free IRQs easily enough in /proc/interrupts).  
     
     What rational goes into choosing another IRQ/Base Address pair for the 
     second card?  Most cards seem to default to IRQ 10 and 0x300.  Is 
     there a normal relationship between the IRQ and Base address (like 
     serial ports and IRQs have)?  Or can I just use any free IRQ/address 
     combination?  
     
     My assumption is that 0x300 is the START of an address range.  How 
     large is the range?  
     
     How does the three byte 0xNNN addressing form relate to the addresses 
     presented in /proc/ioports?  My Linux machines are at home, but my 
     memory is that the file lists ranges using four byte address names.
     
     Also, what is 'full duplex' and do I want it enabled?
     
     TIA,
     Peter
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org