Tags give the ability to mark specific points in history as being important
-
sunxi-dt64-for-4.21
44ff3caf · ·Allwinner arm64 DT changes for 4.21 Our usual set of arm64 DT changes, with the biggest additions being: - Support for the video decoding engine in the A64 - Support for the audio codec in the A64 - USB Support in the H6 - HDMI Support in the H6 - EMAC Support in the H6 - New board: Orange Pi Lite2
-
sunxi-dt-for-4.21
5719ac19 · ·Allwinner DT changes for 4.21 This is a quite big pull request this time, with a huge number of changes (and patches) due to us fixing the vast majority of the DTC warnings our DT had. We also have a bunch of other good, more meaningful, changes: - Support for the new Allwinner T3 (rebranded R40) and f1c100s (armv5) SoCs - AXP803 PMIC AC Power supply support - Rework of the oscillators tree - Two new boards: the t3-cqa3t-bv3 and Lichee Pi Nano Plus a few enhancements here and there. -
sunxi-drivers-for-4.21
d44d37cb · ·Allwinner drivers changes for 4.21 Those patches are all about our SRAM driver, to enable new SoCs: the F1c100s, the H5 and the A64 C1 SRAM, that is used by the video decoding engine.
-
sunxi-core-for-4.21
dabfc836 · ·Allwinner core changes for 4.21 A few patches to enable a new Allwinner SoC based on an armv5 CPU.
-
sunxi-config64-for-4.21
4f49b734 · ·Allwinner arm64 defconfig for 4.21 A bunch of patches to improve the coverage of Allwinner drivers in the arm64 defconfig, mostly targeted at adding display drivers support.
-
sunxi-fixes-for-4.20
5f8208f5 · ·Allwinner fixes for 4.20 One small fix for a regulator range on the Banana Pi M3
-
sound-4.20-rc6
b72f936f · ·sound fixes for 4.20-rc6 Still more incoming fixes than wished at this stage, but all look like small and reasonable fixes. In addition to the usual HD-audio and USB-audio quirks for various devices, two notable changes are included: - A fix for USB-audio UAF at probing a malformed descriptor - Workarounds for PCM rwsem mutex starvation
-
ASB-2018-12-05_4.4-p
8250e54a · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.4
d40633ce · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.14-p-release
ae55a6e8 · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.14-p
8629d9bd · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.14
23bc5181 · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.9-p-release
9ad37d62 · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.9-o-mr1
77d9403b · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.9-o-release
95f6b25d · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.9-p
6aea87e4 · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.9-o
b7ec0d72 · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.9
e16c0406 · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.4-p-release
8593a2fa · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840
-
ASB-2018-12-05_4.4-o-mr1
4af28d38 · ·https://source.android.com/security/bulletin/2018-12-01 CVE-2018-9568 CVE-2018-10840