Search Linux Wireless

[PATCH 1/1] Add uCode/Driver compatibility version number to firmware file name

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

 



Hi all,

Attached please find patch that looks for (requires) new firmware
filenames for 3945 and 4965.

This is to enhance enforcement of driver/uCode compatibility, and allow
simpler coexistence of older/newer drivers and their associated uCode
files.  It also allows easy upgrades of uCode, without modification of
driver, *if* the uCode is compatible (which is likely).

FYI, here's the formula for our version numbers:

The uCode version numbers consist of the following, which are found in
the uCode tarball name, as well as the 1st dword of the firmware file
itself, with following bit offsets:

INTEL_MAJOR:  << 24, internal uCode version number
INTEL_MINOR:  << 16, internal uCode version number
LINUX_MAJOR:  <<  8, (new) indicates driver compatibility
LINUX_MINOR:  <<  0, incremented each time we (Linux team) change
anything

I'm sending the uCode files to Yi separately, so as not to burden
everybody's mailboxes.

Tip of the hat to Jeremy at Red Hat for his help.

-- Ben --

Attachment: 0001-Add-uCode-driver-compatibility-version-number-in-fir.patch
Description: 0001-Add-uCode-driver-compatibility-version-number-in-fir.patch


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux