Loadme121

• Texas Instruments Card Reader Driver
• Texas Instruments Drivers Windows 10

Texas Instruments Inc. DriverHive is a driver updater service that will scan your computer's installed devices, identify the best fitting. The package provides the installation files for Texas Instruments USB 3.0 xHCI Host Controller Driver version 1.0.0.6. If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version.

Port renaming¶

On older udev versions renaming of ethX to swXpY will not be automaticallysupported

In order to rename via udev:

Dual mac mode¶

• The new (cpsw_new.c) driver is operating in dual-emac mode by default, thusworking as 2 individual network interfaces. Main differences from legacy CPSWdriver are:

• optimized promiscuous mode: The P0_UNI_FLOOD (both ports) is enabled inaddition to ALLMULTI (current port) instead of ALE_BYPASS.So, Ports in promiscuous mode will keep possibility of mcast and vlanfiltering, which is provides significant benefits when ports are joinedto the same bridge, but without enabling “switch” mode, or to differentbridges.

• learning disabled on ports as it make not too much sense forsegregated ports - no forwarding in HW.

• enabled basic support for devlink.

Devlink configuration parameters¶

See Documentation/networking/devlink/ti-cpsw-switch.rst

Bridging in dual mac mode¶

The dual_mac mode requires two vids to be reserved for internal purposes,which, by default, equal CPSW Port numbers. As result, bridge has to beconfigured in vlan unaware mode or default_pvid has to be adjusted:

or:

Enabling “switch”¶

The Switch mode can be enabled by configuring devlink driver parameter“switch_mode” to 1/true:

This can be done regardless of the state of Port’s netdev devices - UP/DOWN, butPort’s netdev devices have to be in UP before joining to the bridge to avoidoverwriting of bridge configuration as CPSW switch driver copletly reloads itsconfiguration when first Port changes its state to UP.

When the both interfaces joined the bridge - CPSW switch driver will enablemarking packets with offload_fwd_mark flag unless “ale_bypass=0”

All configuration is implemented via switchdev API.

Bridge setup¶

On/off STP¶

Texas Instruments Card Reader Driver

VLAN configuration¶

Note. This step is mandatory for bridge/default_pvid.

Texas Instruments Drivers Windows 10

Add extra VLANs¶

FDBs¶

FDBs are automatically added on the appropriate switch port upon detection

Manually adding FDBs:

MDBs¶

MDBs are automatically added on the appropriate switch port upon detection

Manually adding MDBs:

Multicast flooding¶

CPU port mcast_flooding is always on

Turning flooding on/off on swithch ports:bridge link set dev sw0p1 mcast_flood on/off

Access and Trunk port¶

Note. Setting PVID on Bridge device itself working only fordefault VLAN (default_pvid).

NFS¶

The only way for NFS to work is by chrooting to a minimal environment whenswitch configuration that will affect connectivity is needed.Assuming you are booting NFS with eth1 interface(the script is hacky andit’s just there to prove NFS is doable).

setup.sh:

run_nfs.sh::

This article describes an issue that occurs when you use a FireWire port-based device in Windows 8.1 or Windows 8. Additional steps of configuration is required to enable this update after the installation.

Symptoms

Assume that you have a computer that equips with an IEEE 1394 FireWire controller card. After you upgrade the computer from Windows 7 to Windows 8.1 or Windows 8, devices that connect to the computer by using a FireWire port do not work.

Cause

This issue occurs because the legacy 1394 bus drivers (1394bus.sys and Ochi1394.sys) are removed in Windows 8.1 or Windows 8.

Resolution

Update information

How to obtain this update

Microsoft Download Center

The following files are available for download from the Microsoft Download Center:

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Additional steps of configuration requirement

After you install the 1394 OHCI Legacy Driver.msi file, follow these steps:

1. Right-click the Legacy1394.inf file under one of the following paths based on the computer's architecture:
   

   • C:Program Files1394 OHCI Compliant Host Controller (Legacy)x86_driver

   • C:Program Files1394 OHCI Compliant Host Controller (Legacy)x64_driver

2. Click Install.

3. Open Device Manager in Control Panel.

4. Expand IEEE 1394 Bus host controllers, and then locate the host controller.

5. Right-click the host controller, and then click Update Driver Software.
   The screen shot of the host controller and the Update Driver Software is listed in the following example:
   

6. Click Browse my computer for driver software.

7. Click Let me pick from a list of device drivers on my computer.

8. Click Generic1394 OHCI compliant host controller (Legacy), and then click the Next button.

9. Click the Close button.

Prerequisites

There are no prerequisites for installing this update.

Registry information

To apply this update, you do not have to make any changes to the registry.

Restart requirement

You have to restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 and Windows 8 file information notesThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are not listed

For all supported x86-based versions of Windows 8.1 or of Windows 8

For all supported x86-based versions of Windows 8.1 or of Windows 8

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section.

More Information

Steps of uninstalling the 1394 OHCI Legacy Driver.msi file

1. Open Control Panel in the Category view.

2. Click Uninstall a program in Control Panel.

3. Right-click 1394 OHCI Compliant Host Controller (Legacy), and then click Uninstall.
   The screen shot of uninstalling the 1394 OHCI Compliant Host Controller (Legacy) is listed in the following example:
   

Additional package information

• This driver is only intended to work with legacy 1394 host controllers. Therefore, you may experience lower transfer data rates than the 1394b driver.

• The driver is intended to resolve compatibility issues for 1394 peripherals on 1394b systems. If you are not experiencing these issues, you should continue to use inbox drivers that are provided in Windows 8.1 or Windows 8.

• You have to reinstall this stand-alone driver package if you upgrade to a newer operating system version in the future.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates