This bug was fixed in the package linux-raspi - 5.4.0-1069.79
---------------
linux-raspi (5.4.0-1069.79) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1069.79 -proposed tracker (LP: #1983941)
* fbtft overlay is missing (LP: #1963919)
- overlays: Add fbtft overlay
[ Ubuntu: 5.4.0-125.141 ]
* focal/linux: 5.4.0-125.141 -proposed tracker (LP: #1983947)
* nbd: requests can become stuck when disconnecting from server with qemu-nbd
(LP: #1896350)
- blk-mq: blk-mq: provide forced completion method
- blk-mq: move failure injection out of blk_mq_complete_request
- nbd: don't handle response without a corresponding request message
- nbd: make sure request completion won't concurrent
- nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed
- nbd: fix io hung while disconnecting device
* CVE-2021-33656
- vt: drop old FONT ioctls
* CVE-2021-33061
- ixgbe: add the ability for the PF to disable VF link state
- ixgbe: add improvement for MDD response functionality
- ixgbevf: add disable link state
-- Juerg Haefliger <[email protected]> Thu, 18 Aug 2022
16:56:14 +0200
** Changed in: linux-raspi (Ubuntu Focal)
Status: In Progress => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33061
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33656
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1963919
Title:
fbtft overlay is missing
Status in linux-raspi package in Ubuntu:
Invalid
Status in linux-raspi source package in Focal:
Fix Released
Status in linux-raspi2 source package in Focal:
Invalid
Status in linux-raspi source package in Impish:
Won't Fix
Status in linux-raspi2 source package in Impish:
Invalid
Status in linux-raspi source package in Jammy:
Fix Released
Status in linux-raspi2 source package in Jammy:
Invalid
Bug description:
[Impact]
To attach TFT touchscreens the pi-foundation kernel ships the fbtft
devicetree overlay along with rpi-display.
While you can attach a stand-alone TFT display just fine when only
using rpi-display to provide the drivers with hardcoded GPIO
assignments, it gets extremely tricky to even enable the touchscreen
input or to use such a TFT with other sensors attached since rpi-
display does not allow any re-assignment of the GPIO pins in use.
The upstream fbtft driver can make use of the already included rpi-display
drivers by defining "rpi-display" in its params. It also allows to freely
re-assign the GPIO pins for backlight, D/C and Reset to give you enough
flexibility to have the display co-exist with any attached sensors and touch
input devices that do not have the ability to re-assign GPIO pins and that
clash with the hardcoded numbering of rpi-display.
An example with freely assigned GPIOs can be seen in the upstream
(rpi-foundation) overlay README file at:
https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884
Please include fbtft in the ubuntu kernels to allow a more flexible
usage of SPI based TFT touchscreens on the Pi.
[Test case]
See above.
[Fix]
Backport commit 6a4525924c43 ("overlays: Add fbtft overlay") from
rpi-5.15.y.
[Where Problems could occur]
Problems might show up when using the new DTB overlay on a Pi
platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1963919/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
