Current status: Already included in 2.6.32-34: 3w-sas: Backported from 2.6.33 in 2.6.32-6 ahci: Cherry-picked support for Intel Cougar Point in 22.214.171.124, 2.6.32-12 ata_generic: add support for Intel IDE-R (60039a5295b3d82a48fe132c699987d2e1408675) ata_piix: Cherry-picked support for Intel Cougar Point in 126.96.36.199, 2.6.32-12 ath9k: Cherry-picked support for AR2427 in 2.6.32-9 atl1c: Cherry-picked support for AR8151 and AR8152 in 2.6.32-28 be2net: Cherry-picked support for BE3 in 188.8.131.52..184.108.40.206, 2.6.32-6..2.6.32-8 e1000e: Cherry-picked support for 82567V-3 in 220.127.116.11, 2.6.32-11 ipheth: Cherry-picked support for iPhone 4 in 2.6.32-22 ixgbe: Cherry-picked support for 82599 X520-P2 in 18.104.22.168, 2.6.32-31 megaraid_sas: Cherry-picked support for 9240 etc. in 2.6.32-39 mpt2sas: Cherry-picked support for SAS2208 in 22.214.171.124, 2.6.32-6 mvsas: Cherry-picked support for ASC-1045/1405 in 126.96.36.199, 2.6.32-11 pata_via: Cherry-picked support for VIA VX900 in 188.8.131.52, 2.6.32-12 qlcnic: Backported from 2.6.36(?) in 2.6.32-28 sfc: Backported from 2.6.33 in 2.6.32-3..2.6.32-9 sky2: Backported from 2.6.35 in 2.6.32-22 vmw_pvscsi: Backported from 2.6.33 in 2.6.32-33 Pending in 2.6.32-35: ar9170usb: Cherry-pick of support for Sphairon Homelink 1202 (and others) bna: Backport from 2.6.38 bnx2i: Cherry-pick of support for BCM5771E bnx2x: Cherry-pick of support for BCM84823 hpsa: Backport from 2.6.38. Removed claim to device IDs handled by cciss pm8001: Backport from 2.6.38 wl1251: Cherry-pick of support for PG11 chips To do (or not): acard-ahci: New driver. Depends on ahci/libahci split so would be tricky to backport. ath9k: add support for newer AR9285 chipsets (53bc7aa08b48e5cd745f986731cc7dc24eef2a9f) ath9k: add support for AR9271 chipset (fb9987d0f748c983bb795a86f47522313f701a08) and AR9300 (db3cc53a2faea2da5730304af06a77d343f314a5) ath9k: add support for the AR9003 2.2 (7284635d2dbc0e055d14bc488c69f8c1d2822ae7) and AR7010 (b176286276f85e10e8ab3342730c5e39e1ce460b) ath9k: add support for AR9485 (1435894dcd263fdbdd5e1ea2a684289dff187c34) atl1c: Add support for AR8151 v2 (8f574b35f22fbb9b5e5f1d11ad6b55b6f35f4533). There are many other changes in the same commit. be2iscsi: Add support for BE3 (f98c96b0b6572b5491e954148509b20f08f31491). This was a new driver in 2.6.32 and based on subsequent commits appears to be quite broken. I would suggest a wholesale backport. be2net: add support for Lancer (fe6d2a38b2076cba515dc95b5dc1589a7ab51c17) bnx2x: Add 57712 support (f2e0899f0f275cc3f5e9c9726178d7d0ac19b2db). This makes many changes to existing code and will need testing on old and new devices. carl9170: New driver, but seems to be meant as a replacment for ar9170usb and has the same device IDs. cnic: Add support for 57712 device (ee87a82a28cddbb9267a294172ecb3d3d3bdaa6c). Probably depends on bnx2x. cx82310_eth: new driver cxgb4: new driver cxgb4i: new driver e1000: add support for CE4100 (5377a4160bb65ee4dd11b4b1d081d86d56d92bff); probably not important e1000e: add support for 82567V-4 (10df0b9116e2039d5585a196753e5f36d7afcba2) e1000e: add support for 82579 (d3738bb8203acf8552c3ec8b3447133fc0938ddd) fs_enet: add support for MPC512x (60ab4361adc188fb47da1c4892cc7a2bb621efef) greth: new driver i2400m: add support for IWL6050 (7329012e673231dee9a21567cfb9881f5ea462ba) igb: Add support for 82580 and 82576NS. Dependencies are complex. (#574523) igb: add support for 82576 ET2 (b894fa2627e28c078740dc7041cd08c7e2c353ab) igb: add support for I350 (d2ba2ed8fe3aa796a671a6922119d7171bb49515) igb: Add support for DH89xxCC (308fb39a860c816be8741fe783ae7c64e9c1af5d) ipr: add device IDs for new hardware (d7b4627f5f3390a2f350f16c047b3fc3eccce6d8) iwlagn: update PCI ID for 6000g2a series devices (fb30eaf38703d7562606e49a5872745d66366a50), update PCI ID for 6000g2b series devices (8b37d9f0a1e114a1c7f5082842fb310a81ea3732) iwlwifi: add support for 6000g2 NIC (1780221141047c83c99f9d02b504700080cc35c9), 6000 Series 2x2 AGN Gen2 (0b5af201b25334f7b9c991b2800693dd4cb4b5f7) iwlwifi: enable 6000 and 6050 series Gen2 devices (0326433995ad43b64ebabdd2390a5d11f33f025b, 1808972f16adba592ceb10a47dee42ef8ee39cee, 79d07325502e73508f917475bc1617b60979dd94) iw_cxgb4: new driver ixgbe: add support for 82599 10GBASE-T device (119fc60a2d20b63439fdae99f0c7022d3dd99def) #609191 ixgbe: add support for x540 MAC (b93a22260f6f4bcf6c92c54de8530a97d3e921f0) ks8842: Add Micrel KS8841/42 support (28bd620c7a1244e59459d6293ca11f162e0a67b9) ksz884x: new driver megaraid_sas: Add 9565/9285 specific code (9c915a8c99bce637226aa09cb05fc18486b229cb) mwl8k: Add support for 88w8366. Dependencies are complex. octeon_mgmt: new driver; platform driver orinoco_usb: new driver pata_samsung_cf: new driver; platform driver pch_gbe: new driver; probably not useful phy/broadcom: Add 5241 support (7a938f80264f2cbfb0c0841b450eab42a8093281) phy/marvell: add 88ec048 support (3ff1c25927e3af61c6bf0e4ed959504058ae4565) pxa168_eth: new driver; platform driver qeth: support the new OSA CHPID types OSX and OSM (5113fec0984276836cb6f0677f7cb53586ec3451) qla2xxx: add support for ISP82XX support (a9083016a5314b3aeba6e0d2e814872e72168c08, f1af6208c8cef81e313ec2e64b44e783c3a11c13) r8169: more 8168dp support (e6de30d63eb17c5cbb7affdfc71df95286bfa7d9) rt2x00: add support for RT2800P/RT2800E family; probably redundant with rt2860sta rt2x00: Add initial support for RT3370/RT3390 devices (f93bc9b3ce379800b30b3c2f4fc945ae35a80039); not sure what to do with this rt73usb: add support for WLI-U2-H54HP (050e8a47dc8b056c880f380ffd01055669f8fe68) rtl8192ce: new driver sata_dwc_460ex: new driver; platform driver smsc75xx: new driver tg3: Add support for 5717 and 57765. Dependencies are complex. uas: new driver Priorities: Of the existing drivers, I would guess that ath9k, e1000e, igb, iwlagn, iwlwifi, r8169, rt2x00 and tg3 are the most widely used. Unfortunately they are also updating quite frequently and likely to be hard to cherry-pick changes from. So I think we should do some combination of: 1. Look at what other distributions with Linux 2.6.32 have done with these 2. Ask for guidance from the upstream maintainers 3. Where the driver is vendor-maintained, request that the vendor tests the backport 4. Try to get broad testing by users in s-p-u or a separate repository We have fairly limited time to do this before 6.0.2 so whatever we do we need to move fast. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Description: This is a digitally signed message part