linux-kernel - Re: [PATCH] drm/rockchip: cdn-dp: Remove redundant workarounds for firmware loading

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240710-smooth-hypnotic-raccoon-b91fba@houat>
Date: Wed, 10 Jul 2024 09:13:17 +0200
From: Maxime Ripard <mripard@...nel.org>
To: Dragan Simic <dsimic@...jaro.org>
Cc: Andy Yan <andyshrk@....com>, linux-rockchip@...ts.infradead.org, 
	dri-devel@...ts.freedesktop.org, heiko@...ech.de, hjc@...k-chips.com, andy.yan@...k-chips.com, 
	maarten.lankhorst@...ux.intel.com, tzimmermann@...e.de, airlied@...il.com, daniel@...ll.ch, 
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, javierm@...hat.com
Subject: Re: [PATCH] drm/rockchip: cdn-dp: Remove redundant workarounds for
 firmware loading

On Tue, Jul 09, 2024 at 06:36:08PM GMT, Dragan Simic wrote:
> > > > > As I already wrote earlier, and as the above-linked discussions
> > > > > conclude, solving these issues doesn't belong to any specific driver.
> > > > > It should be resolved within the kernel's firmware loading mechanism
> > > > > instead, and no driver should be specific in that regard.
> > > >
> > > > IT would be good if it can be resolved within the kernel's  firmware
> > > > loading mechanism.
> > > 
> > > ... we'll need this as a systemic solution.
> > 
> > The general policy has been to put drivers that need a firmware as a
> > module, and just never build them statically.
> 
> I totally agree, but if Buildroot builds them statically and provides
> no initial ramdisk, we need a better solution than having various drivers
> attempt to implement their own workarounds.

Buildroot typically allows custom kernel configurations, so it's not
really "enforcing" anything like another distro does.

It is definitely targetted towards very stripped down systems, so I
guess building the drivers statically is a natural choice, but it works
fine with modules too.

Maxime

Download attachment "signature.asc" of type "application/pgp-signature" (274 bytes)