diff options
author | John Crispin <blogic@openwrt.org> | 2015-10-26 09:01:05 +0000 |
---|---|---|
committer | John Crispin <blogic@openwrt.org> | 2015-10-26 09:01:05 +0000 |
commit | 7cc0f6e3bcead0a27956704cd1b105aa5f805e4f (patch) | |
tree | 3bad1f36686ac6caa692c4e386b843c68e592066 /target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch | |
parent | df51f2916b87b0c54a0d60932257c9288c845e62 (diff) | |
download | master-187ad058-7cc0f6e3bcead0a27956704cd1b105aa5f805e4f.tar.gz master-187ad058-7cc0f6e3bcead0a27956704cd1b105aa5f805e4f.tar.bz2 master-187ad058-7cc0f6e3bcead0a27956704cd1b105aa5f805e4f.zip |
brcm2708: update 4.1 patches
As usual, this patches were taken (and rebased) from
https://github.com/raspberrypi/linux/commits/rpi-4.1.y
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47258 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch')
-rw-r--r-- | target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch b/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch index 8f62474477..caed159645 100644 --- a/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch +++ b/target/linux/brcm2708/patches-4.1/0080-Fix-driver-detection-failure-Check-that-the-buffer-r.patch @@ -1,7 +1,7 @@ -From 0e76c9361112e7a88d08b3bf3d23c6ba936de01e Mon Sep 17 00:00:00 2001 +From 1cefedfe457ea7c738ab1c10ec88fd8a5632444a Mon Sep 17 00:00:00 2001 From: Gordon Hollingworth <gordon@fiveninjas.com> Date: Tue, 23 Jun 2015 09:53:40 +0100 -Subject: [PATCH 080/171] Fix driver detection failure Check that the buffer +Subject: [PATCH 080/203] Fix driver detection failure Check that the buffer response is non-zero meaning the touchscreen was detected --- |