On Tue, Mar 23, 2021 at 02:05:23PM +0200, Eli Billauer wrote:
> On 22/03/21 13:11, Greg KH wrote:
> >
> > > XILLYBUS and XILLYBUS_PCIE are currently enabled as M in several Linux
> > > distributions. Making them depend on, rather than select XILLYBUS_CLASS is
> > > likely to disable the driver in
>> i assume you set this option in the config.txt? This shouldn't have any
>> affect for the mainline kernel / DT.
> I am aware of that...
I include my config.txt on RPi4B for reference...
arm_64bit=1
enable_uart=1
upstream_kernel=1
kernel=vmlinuz-5.10.0-5-rt-arm64
initramfs
allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a004-20210328
i386 randconfig-a003-20210328
i386 randconfig-a001-20210328
i386 randconfig-a002-20210328
i386
randconfig-a004-20210328
i386 randconfig-a003-20210328
i386 randconfig-a001-20210328
i386 randconfig-a002-20210328
i386 randconfig-a006-20210328
i386 randconfig-a005-20210328
x86_64
Hi Stefan, thank you for your response.
> i assume you set this option in the config.txt? This shouldn't have any
> affect for the mainline kernel / DT.
I am aware of that...
I did "snd_bcm2835 enable_hdmi=0" in /etc/modules.
"modinfo snd_bcm2835" shows as below. Doesn't it indicate snd_bcm2835
Hi,
Am 28.03.21 um 07:58 schrieb Ryutaroh Matsumoto:
>> I think the root cause of this issue is that both vc4.ko and snd_bcm2835.ko
>> try to provide ALSA sinks to HDMI audio outputs from RPi.
>> Why do the two drivers provide the same functionality for the same device?
>> It seems nonsense.
>>
