This bug was fixed in the package linux-raspi - 5.19.0-1002.6
---
linux-raspi (5.19.0-1002.6) kinetic; urgency=medium
* kinetic/linux-raspi: 5.19.0-1002.6 -proposed tracker (LP: #1991077)
* VM fails to boot in ScalingStack (LP: #1990995)
- [Packaging] raspi: Include virtio
** Tags added: kern-3230
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1918583
Title:
Switch to libgpiod and disable CONFIG_GPIO_SYSFS
Status in linux package in Ubuntu:
Confirmed
Now that jammy's out (which still includes CONFIG_GPIO_SYSFS), let's at
least consider this for kinetic. I would suggest it would sensible to at
least try this in an interim release prior to the next LTS. There will
undoubtedly be things that break, but it's probably better to be aware
of how much
This post: https://waldorf.waveform.org.uk/2021/the-pins-they-
are-a-changin.html should explain things rather more completely than I
can here but the TL;DR version is: it would be nice to disable sysfs but
there's *way* too much stuff that would break right now if we did
(mostly Python GPIO
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1918583
Title:
Switch to libgpiod and disable CONFIG_GPIO_SYSFS
5 matches
Mail list logo
