linux/drivers, branch mybooklive

gpl-source-mybooklive-02.32.05-044.zip

2014-08-13T23:40:43Z

gpl-source-mybooklive-02.11.09-053.zip

2014-08-13T23:39:02Z

gpl-source-mybooklive-02.10.09-124.zip

2014-08-13T23:32:56Z

gpl-source-mybooklive-020202.zip

2014-08-13T23:11:53Z

gpl-source-mybooklive-020035.zip

2014-08-13T23:04:11Z

gpl-source-mybooklive-010203-update.zip

2014-08-13T21:29:15Z

gpl-source-mybooklive-010002-update.zip

2014-08-13T21:14:13Z

s3cmci: initialize default platform data no_wprotect and no_detect with 1

2010-04-01T22:58:56Z

commit c212808a1ba6bfba489006399b8152a047305acf upstream. If no platform_data was givin to the device it's going to use it's default platform data struct which has all fields initialized to zero. As a result the driver is going to try to request gpio0 both as write protect and card detect pin. Which of course will fail and makes the driver unusable Previously to the introduction of no_wprotect and no_detect the behavior was to assume that if no platform data was given there is no write protect or card detect pin. This patch restores that behavior. Signed-off-by: Lars-Peter Clausen Cc: Ben Dooks Cc: Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman

b43: Workaround circular locking in hw-tkip key update callback

2010-04-01T22:58:55Z

commit 96869a39399269a776a94812e9fff3d38b47d838 upstream The TKIP key update callback is called from the RX path, where the driver mutex is already locked. This results in a circular locking bug. Avoid this by removing the lock. Johannes noted that there is a separate bug: The callback still breaks on SDIO hardware, because SDIO hardware access needs to sleep, but we are not allowed to sleep in the callback due to mac80211's RCU locking. Signed-off-by: Michael Buesch Tested-by: Larry Finger Reported-by: kecsa@kutfo.hit.bme.hu Cc: Johannes Berg Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ahci: use BIOS date in broken_suspend list

2010-04-01T22:58:54Z

commit 9deb343189b3cf45e84dd08480f330575ffe2004 upstream. HP is recycling both DMI_PRODUCT_NAME and DMI_BIOS_VERSION making ahci_broken_suspend() trigger for later products which are not affected by the original problems. Match BIOS date instead of version and add references to bko's so that full information can be found easier later. This fixes http://bugzilla.kernel.org/show_bug.cgi?id=15462 Signed-off-by: Tejun Heo Reported-by: tigerfishdaisy@gmail.com Signed-off-by: Jeff Garzik Signed-off-by: Greg Kroah-Hartman