Home
last modified time | relevance | path

Searched refs:BUS (Results 1 – 23 of 23) sorted by relevance

/linux-2.6.39/arch/mn10300/include/asm/
Dpci.h22 #define __pcidebug(FMT, BUS, DEVFN, WHERE,...) \
25 (BUS)->number, \
33 #define __pcidebug(FMT, BUS, DEVFN, WHERE, ...) do {} while (0) argument
/linux-2.6.39/arch/sparc/kernel/
Dpsycho_common.h14 #define PSYCHO_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
15 (((unsigned long)(BUS) << 16) | \
Dprom_irqtrans.c101 #define SABRE_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
102 (((unsigned long)(BUS) << 16) | \
Dpci_schizo.c72 #define SCHIZO_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
73 (((unsigned long)(BUS) << 16) | \
/linux-2.6.39/Documentation/frv/
Dmmu-layout.txt47 E0000000 - EFFFFFFF L-BUS CS2# VDK SLBUS/PCI window
48 F0000000 - F0FFFFFF L-BUS CS5# MB93493 CSC area (DAV daughter board)
49 F1000000 - F1FFFFFF L-BUS CS7# (CB70 CPU-card PCMCIA port I/O space)
50 FC000000 - FC0FFFFF L-BUS CS1# VDK MB86943 config space
51 FC100000 - FC1FFFFF L-BUS CS6# DM9000 NIC I/O space
52 FC200000 - FC2FFFFF L-BUS CS3# MB93493 CSR area (DAV daughter board)
53 FD000000 - FDFFFFFF L-BUS CS4# (CB70 CPU-card extra flash space)
55 FF000000 - FF1FFFFF L-BUS CS0# Flash 1
56 FF200000 - FF3FFFFF L-BUS CS0# Flash 2
57 FFC00000 - FFC0001F L-BUS CS0# FPGA
/linux-2.6.39/Documentation/i2c/busses/
Di2c-sis559557 is a BUS driver, not a CHIP driver. A BUS driver is used by other CHIP
/linux-2.6.39/Documentation/scsi/
Dsym53c8xx_2.txt39 10.2.6 Check SCSI BUS
47 10.4 SCSI BUS checking boot option
385 The driver will try to send a BUS DEVICE RESET message to the target.
476 10.2.6 Check SCSI BUS
560 10.4 SCSI BUS checking boot option.
565 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
566 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
567 Unfortunately, the following common SCSI BUS problems are not detected:
630 Data parity error detected on the PCI BUS.
639 BF (0x20), then the cause may be likely due to a PCI BUS problem.
[all …]
Dncr53c8xx.txt52 10.2.19 Check SCSI BUS
59 10.6 SCSI BUS checking boot option
544 The driver will try to send a BUS DEVICE RESET message to the target.
820 10.2.19 Check SCSI BUS
852 when it arbitrated for the SCSI BUS.
878 SCSI BUS check do not attach on error buschk:1
994 10.6 SCSI BUS checking boot option.
999 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
1000 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
1001 Unfortunately, the following common SCSI BUS problems are not detected:
[all …]
DChangeLog.sym53c8xx238 that overclocked PCI BUS up to 48 MHz will not be refused.
239 The more the BUS is overclocked, the less the driver will
293 from a device that has received a BUS DEVICE RESET message from
310 - Add the control command 'resetdev' that allows to send a BUS
322 present and IGNORE WIDE RESIDUE message on the BUS at the same time).
411 kinds of screw-up that may happen on the SCSI BUS.
DChangeLog.sym53c8xx_235 Misdetection of BUS mode was triggered on module reload only,
DChangeLog.ncr53c8xx487 This option enables checking of SCSI BUS data lines after SCSI
DChangeLog.1992-19971424 * aha1542.c (aha1542_reset): Try BUS DEVICE RESET, and then pass
/linux-2.6.39/arch/arm/plat-s3c24xx/
DKconfig113 SPI GPIO configuration code for BUS 1 when connected to
119 SPI GPIO configuration code for BUS 1 when connected to
/linux-2.6.39/Documentation/networking/
Darcnet-hardware.txt35 There are two "types" of ARCnet - STAR topology and BUS topology. This
38 BUS cards to BUS cards. That makes sense, right? Well, it's not quite
98 Cards for coax cabling are shipped in two different variants: for BUS and
100 lies in the hybrid chip installed. BUS cards use high impedance output,
156 The BUS topology is very similar to the one used by Ethernet. The only
160 cable. A typical BUS ARCnet network looks like:
165 B - BUS type card
180 BUS network in place of a BUS card and a terminator:
185 But, according to my own experiments, you can simply hang a BUS type card
245 hubs in a large network is a bad idea. The maximum length of a single "BUS
[all …]
Dcan.txt704 "ERROR-WARNING", "ERROR-PASSIVE", "BUS-OFF" or "STOPPED"
/linux-2.6.39/Documentation/sound/alsa/
Dhda_codec.txt86 Each codec chip on the board is then created on the BUS instance.
92 The first argument is the BUS instance, the second argument is the
/linux-2.6.39/arch/m32r/platforms/mappi/
Ddot.gdbinit.smp83 # BUS
/linux-2.6.39/Documentation/
Ddebugging-via-ohci1394.txt116 ieee1394: Node added: ID:BUS[0-01:1023] GUID[0090270001b84bba]
Dedac.txt66 PCI BUS SCANNING
DDMA-API-HOWTO.txt536 in some ports the mapping is per each BUS so less devices contend for the
/linux-2.6.39/drivers/eisa/
Deisa.ids77 AIR3001 "ENET2E EISA BUS MASTER ETHERNET ADAPTER"
78 AIR3101 "ENET-2V LOCAL BUS MASTER ETHERNET ADAPTER"
1072 KCI3201 "ET32EM EISA 32-bit BUS-MASTER Ethernet Adapter"
1172 PLX1001 "OCEAN EISALink EISA 32-Bit BUS-MASTER Ethernet Controller"
1264 USC0340 "UltraStor - ULTRA-34F VESA VL-BUS Host Adapter"
/linux-2.6.39/Documentation/spi/
Dspi-summary494 BUS NUMBERING
/linux-2.6.39/
DMAINTAINERS620 ARM PRIMECELL BUS SUPPORT
4628 OPENCORES I2C BUS DRIVER
4798 PCA9541 I2C BUS MASTER SELECTOR DRIVER
4804 PCA9564/PCA9665 I2C BUS DRIVER
6736 VLYNQ BUS
6781 W1 DALLAS'S 1-WIRE BUS