| 2019-06-07 14:44:30 |
Paolo Pisati |
bug |
|
|
added bug |
| 2019-06-07 14:56:47 |
Paolo Pisati |
summary |
Enable the Qualcomm DB820C board |
Initial support for Qualcomm Snapdragon 820 chipset |
|
| 2019-06-07 15:11:12 |
Paolo Pisati |
description |
Impact:
The bionic/snapdragon kernel should work on qcom410 and qcom820 chipsets, but due to some bugs, it never booted on any qcom820 board (e.g. Qualcomm DB820C APQ8096).
Fix:
Import all the necessary patches (see the pull request below).
How to test:
1) put the board in fastboot mode (see [1])
2) generate a compatible boot.img:
$ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x80000000 --kernel_offset 0x8000 --ramdisk_offset 0x1000000 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b0000' --output bionic-snapdragon-db820c-boot.img
3) fastboot the board using the freshly generated boot.img:
$ fastboot boot bionic-snapdragon-db820c-boot.img
Regression potential:
With new code there's always a degree of regression potential, but all patches (but one) were cherry-picked from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree.
1: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html |
Impact:
Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing
tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm
DB820C APQ8096).
Fix:
Import the necessary patches to make it boot on such board (and clones).
How to test:
1) put the board in fastboot mode (see [2])
2) generate a compatible boot.img:
$ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x80000000 --kernel_offset 0x8000 --ramdisk_offset 0x1000000 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b0000' --output bionic-snapdragon-db820c-boot.img
3) boot the board using the generated boot.img:
$ fastboot boot bionic-snapdragon-db820c-boot.img
Regression potential:
With new code there's always a degree of regression potential, but all patches
(but one) came from Linus's upstream tree, and the only external one, came
direclty from the qcom-lt 4.14 tree.
1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html |
|
| 2019-06-07 15:12:00 |
Paolo Pisati |
description |
Impact:
Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing
tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm
DB820C APQ8096).
Fix:
Import the necessary patches to make it boot on such board (and clones).
How to test:
1) put the board in fastboot mode (see [2])
2) generate a compatible boot.img:
$ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x80000000 --kernel_offset 0x8000 --ramdisk_offset 0x1000000 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b0000' --output bionic-snapdragon-db820c-boot.img
3) boot the board using the generated boot.img:
$ fastboot boot bionic-snapdragon-db820c-boot.img
Regression potential:
With new code there's always a degree of regression potential, but all patches
(but one) came from Linus's upstream tree, and the only external one, came
direclty from the qcom-lt 4.14 tree.
1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html |
Impact:
Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096).
Fix:
Import the necessary patches to make it boot on such board (and clones).
How to test:
1) put the board in fastboot mode (see [2])
2) generate a compatible boot.img:
$ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x80000000 --kernel_offset 0x8000 --ramdisk_offset 0x1000000 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b0000' --output bionic-snapdragon-db820c-boot.img
3) boot the board using the generated boot.img:
$ fastboot boot bionic-snapdragon-db820c-boot.img
Regression potential:
With new code there's always a degree of regression potential, but all patches (but one) came from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree.
1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html |
|
| 2019-06-07 15:19:16 |
Paolo Pisati |
description |
Impact:
Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096).
Fix:
Import the necessary patches to make it boot on such board (and clones).
How to test:
1) put the board in fastboot mode (see [2])
2) generate a compatible boot.img:
$ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x80000000 --kernel_offset 0x8000 --ramdisk_offset 0x1000000 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b0000' --output bionic-snapdragon-db820c-boot.img
3) boot the board using the generated boot.img:
$ fastboot boot bionic-snapdragon-db820c-boot.img
Regression potential:
With new code there's always a degree of regression potential, but all patches (but one) came from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree.
1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html |
Impact:
Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096).
Fix:
Import the necessary patches to make it boot on such board (and clones).
How to test:
1) put the board in fastboot mode (see [2])
2) generate a compatible boot.img:
$ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x80000000 --kernel_offset 0x8000 --ramdisk_offset 0x1000000 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b0000' --output bionic-snapdragon-db820c-boot.img
3) boot the board using the generated boot.img:
$ fastboot boot bionic-snapdragon-db820c-boot.img
Regression potential:
With new code there's always a degree of regression potential, but all patches (but one) came from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree.
1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html |
|
| 2019-06-07 15:19:50 |
Paolo Pisati |
description |
Impact:
Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096).
Fix:
Import the necessary patches to make it boot on such board (and clones).
How to test:
1) put the board in fastboot mode (see [2])
2) generate a compatible boot.img:
$ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x80000000 --kernel_offset 0x8000 --ramdisk_offset 0x1000000 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b0000' --output bionic-snapdragon-db820c-boot.img
3) boot the board using the generated boot.img:
$ fastboot boot bionic-snapdragon-db820c-boot.img
Regression potential:
With new code there's always a degree of regression potential, but all patches (but one) came from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree.
1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html |
Impact:
Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096).
Fix:
Import the necessary patches to make it boot on such a board (and clones).
How to test:
1) put the board in fastboot mode (see [2])
2) generate a compatible boot.img:
$ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
$ touch ramdisk
$ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x80000000 --kernel_offset 0x8000 --ramdisk_offset 0x1000000 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b0000' --output bionic-snapdragon-db820c-boot.img
3) boot the board using the generated boot.img:
$ fastboot boot bionic-snapdragon-db820c-boot.img
Regression potential:
With new code there's always a degree of regression potential, but all patches (but one) came from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree.
1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html |
|
| 2019-07-02 09:08:28 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-07-02 09:08:28 |
Kleber Sacilotto de Souza |
bug task added |
|
linux-snapdragon (Ubuntu Bionic) |
|
| 2019-07-02 09:08:40 |
Kleber Sacilotto de Souza |
linux-snapdragon (Ubuntu): status |
New |
Invalid |
|
| 2019-07-02 09:18:53 |
Kleber Sacilotto de Souza |
linux-snapdragon (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
linux-snapdragon (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
cve linked |
|
2018-12126 |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
cve linked |
|
2018-12127 |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
cve linked |
|
2018-12130 |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
cve linked |
|
2019-11085 |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
cve linked |
|
2019-11091 |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
cve linked |
|
2019-11815 |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
cve linked |
|
2019-11833 |
|
| 2019-07-22 10:56:14 |
Launchpad Janitor |
cve linked |
|
2019-11884 |
|
