Lines Matching full:driver
30 .Nd "QLogic NetXtreme II (BCM5706/5708/5709/5716) PCI/PCIe Gigabit Ethernet adapter driver"
32 To compile this driver into the kernel,
40 Alternatively, to load the driver as a
49 driver supports QLogic's NetXtreme II product family, including the
59 driver under
79 driver supports the following media types:
125 driver supports the following media options:
138 driver provides support for various NICs based on the QLogic NetXtreme II
209 Set the number of memory pages assigned to receive packets by the driver.
214 by the driver.
268 The driver has encountered a fatal initialization error.
270 The driver has encountered a fatal initialization error.
272 The driver does not support the controller revision in use.
274 The driver has encountered a fatal initialization error.
276 The driver could not access the controller NVRAM correctly.
278 The driver could not allocate DMA memory to setup the controllers
281 The driver could not create a network interface for the controller.
283 The driver could not access the PHY used by the controller.
285 The driver could not initialize the IRQ handler.
287 The driver could not read a PHY register before the timeout period expired.
289 The driver could not write to the PHY register because a timeout occurred.
291 The driver could not write to NVRAM because a timeout occurred.
293 The driver does not recognize the NVRAM device being used and therefore
296 The driver cannot read NVRAM or the NVRAM is corrupt.
298 The driver cannot read NVRAM or the NVRAM is corrupt.
300 The driver cannot read NVRAM or the NVRAM is corrupt.
302 The driver was unable to map memory into DMA addressable space required
305 The driver could not allocate a PCI compatible DMA tag.
307 The driver could not allocate a DMA tag for the controller's
310 The driver could not allocate DMA addressable memory for the controller's
313 The driver could not map the status block memory into the controller's DMA
316 The driver could not allocate a DMA tag for the controller's
319 The driver could not allocate DMA addressable memory for the controller's
322 The driver could not map the statistics block memory into the controller's DMA
325 The driver could not allocate a DMA tag for the controller's
328 The driver could not allocate DMA addressable memory for the controller's
331 The driver could not map the TX descriptor chain memory into the controller's DMA
334 The driver could not allocate a DMA tag for the controller's
337 The driver could not map the TX mbuf memory into the controller's DMA
340 The driver could not allocate a DMA tag for the controller's
343 The driver could not allocate DMA addressable memory for the controller's
346 The driver could not map the RX descriptor chain memory into the controller's DMA
349 The driver could not allocate a DMA tag for the controller's
352 The driver could not map the RX mbuf memory into the controller's DMA
355 The driver was not able to synchronize with the firmware running on the
359 The driver was not able to read a valid Ethernet MAC address from NVRAM.
361 The driver has encountered a fatal initialization error.
363 The driver has encountered a fatal initialization error.
367 The driver has encountered a fatal initialization error.
369 The driver has encountered a fatal initialization error.
371 The driver could not map a RX mbuf into DMA addressable memory.
373 The driver was unable to allocate enough mbufs to fill the RX chain
379 The driver was unable to allocate a new mbuf for the RX chain and reused
390 The driver could not map a TX mbuf into DMA addressable memory.
392 The driver received an error while attempting to register the poll function.
394 Changing the VLAN MTU is not currently supported by the driver.
399 Disabling VLAN tag stripping is not currently supported by the driver.
402 with the cable connection, or a driver logic problem has occurred..
424 device driver first appeared in
429 driver was written by