Mauro Carvalho Chehab
Mauro Carvalho Chehab
> @mchehab I managed to fix the devicetree doc by moving the footnote to the end of the file > ... > There are two references to that footnote in...
Version 0.7.0 uses a new event to monitor disk errors. It requires Kernel 5.18 or upper. Hopefully this should help with the issue.
As an update, libevent is an early version of a code that was later packaged as libtraceevent. I updated rasdaemon to use libtraceevent after version 0.7.0. This should hopefully help...
Merged, thanks!
Basically, libevent is an early version of a code that was later packaged as libtraceevent. I updated it to use libtraceevent after version 0.7.0. This should hopefully help solving issues...
The changes you're proposing seem incomplete, as you just defined two new macros but the logic is not using it. Did you forget to push some other changes? Also, please...
> > While we are here, perhaps you could also propose some persistent rules for DVB devices. IMO, such rule should get the device name via [DVB frontend API's FE_GET_INFO...
Adding a DVB device name to uevent seems trivial (patch untested): ``` [PATCH] media: dvbdev: export adapter's name to DVB uevent variables That helps adding a persistent rule for DVB,...
Added a [Linux Kernel patch](https://lore.kernel.org/linux-media/[email protected]/T/#mb2956b97a996a5047020402d7d1613e683e4826e) adding two variables to DVB uevent: ``` /sys/class/dvb/dvb0.demux0/uevent:DVB_ADAPTER_NAME=PCTV nanoStick T2 290e /sys/class/dvb/dvb0.demux0/uevent:DVB_ADAPTER_PDEV=2-1:1.0 /sys/class/dvb/dvb0.dvr0/uevent:DVB_ADAPTER_NAME=PCTV nanoStick T2 290e /sys/class/dvb/dvb0.dvr0/uevent:DVB_ADAPTER_PDEV=2-1:1.0 /sys/class/dvb/dvb0.frontend0/uevent:DVB_ADAPTER_NAME=PCTV nanoStick T2 290e /sys/class/dvb/dvb0.frontend0/uevent:DVB_ADAPTER_PDEV=2-1:1.0 /sys/class/dvb/dvb0.net0/uevent:DVB_ADAPTER_NAME=PCTV nanoStick T2...
Btw, there was a previous attempt to have persistent names for DVB devices: https://lore.kernel.org/linux-media/153778383104.14867.1567557014782141706.stgit@warthog.procyon.org.uk/ The issue is that some boards have multiple adapters sharing the same parent device. On well-behavored...