The le driver supports reception and transmission of extended frames for vlan 4. The default buffer size is large enough to hold a maximum-size Ethernet packet. This parameter is used only if a specific memory region is provided to the driver. The software interface to the driver is divided into three parts. Current internal support for this mechanism is not robust; implementation may not work on all targets requiring these restrictions. A value of zero indicates that the default buffer size should be used. Skip site navigation 1 Skip section navigation 2 Header And Logo.

Uploader: Gora
Date Added: 13 March 2016
File Size: 15.72 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 85722
Price: Free* [*Free Regsitration Required]

This is potentially a hardware fail- ure. No jumpering diagram is necessary. The driver can be configured to support big-endian or little-endian architectures. The le driver allows the selection of the following media types via ifconfig 8 with these on-board interfaces: This parameter can be used to specify the number of bytes of access width to be used by the driver ajd access to the shared memory.

It contains error recovery code to handle known device errata related to DMA activity. Use of this parameter should be rare. If the cpu board hardware automatically swaps all am accesses to and from the PCI bus, then input and output byte stream need not aam79c970 swapped.

The chip still has to be programmed to operated in little endian mode as it is on the PCI bus. The LANCE control register 3 determines the bus mode of the device, allowing the support of big-endian and little-endian architectures.


The driver assumes that this address is available in a global, six-byte character array, lnEnetAddr[].

AM79C Datasheet(PDF) – Advanced Micro Devices

This value can be used to determine the distance from the Ethernet tap to the point on the Ethernet cable that is shorted or open unterminated. This parameter can be used to explicitly limit the amount of shared memory bytes this driver will use. Generally, the le driver aims at supporting as many different chips on as many different platforms as possible, partially at the cost of the best performance with some of these. The optionally reported TDR value is an internal counter of the interval between the start of a transmission and the occurrence of a collision.

Thus the pcn 4 driver should be preferred for the latter. The software interface to the driver is divided into three parts. If a memory region is provided to the driver, the size of this region is adjustable to suit user needs.

The NetBSD version in turn was derived from the le driver which first appeared in 4. The default value supports Motorola-type buses. It indicates to the driver where to find the RDP register. Network performance will be affected, since the target will no longer be able to receive all valid packet sizes. The default buffer size is large enough to hold a maximum-size Ethernet packet.

When using autoselection, a default media type is selected for use by examining all ports for carrier. Note that unlike the pcn 4 driver, the le driver does not support selecting Mbps Fast Ethernet media types. It assumes that this shared memory is directly available to it without any arbitration or timing concerns.


The first media type with which a car- rier is detected will be selected. Therefore, in the global interface structure, the function pointer to the initialization routine is NULL. In such cases all the registers which the chip DMA s to have to be swapped and written to, so that when the hardware swaps the accesses, the chip would see them correctly.

FreeBSD Manual Pages

To achieve this, the driver must be given several target-specific parameters, and some external support routines must be provided. This includes a superset of the PCI bus Ethernet chips supported by the pcn 4 driver. Skip site navigation 1 Skip section navigation 2 Header And Logo. This array is typically created and stuffed by the BSP code. Code size text varies greatly between architectures and is therefore not quoted here.

This driver is designed to be moderately generic, operating unmodified across the range of architectures and targets supported by VxWorks.