[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACO55ts5C6xodqstoeCvhpRpMOB=nTTPDnBfN_QT2GJe2F4wNw@mail.gmail.com>
Date: Fri, 23 Jul 2021 20:48:19 +0200
From: Karol Herbst <kherbst@...hat.com>
To: Arnd Bergmann <arnd@...nel.org>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Ben Skeggs <bskeggs@...hat.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>, Lyude Paul <lyude@...hat.com>,
Arnd Bergmann <arnd@...db.de>,
nouveau <nouveau@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Nikola Cornij <nikola.cornij@....com>
Subject: Re: [PATCH] drm/nouveau/kms/nv50-: fix build failure with CONFIG_BACKLIGHT=n
On Fri, Jul 23, 2021 at 8:40 PM Arnd Bergmann <arnd@...nel.org> wrote:
>
> On Fri, Jul 23, 2021 at 6:34 PM Karol Herbst <kherbst@...hat.com> wrote:
> > On Fri, Jul 23, 2021 at 6:31 PM Randy Dunlap <rdunlap@...radead.org> wrote:
> > > On 7/23/21 8:15 AM, Karol Herbst wrote:
> > > > On Fri, Jul 23, 2021 at 5:10 PM Randy Dunlap <rdunlap@...radead.org> wrote:
> > > >
> > > > what's actually the use case of compiling with
> > > > CONFIG_DRM_NOUVEAU_BACKLIGHT=n anyway?
> > >
> > > Dunno. In this case it was just a randconfig. Still, it needs to be
> > > handled in some way - such as the other suggestion in this thread.
> > >
> >
> > sure, I was just curious if there was a specific use case or just
> > something random as you mentioned.
>
> I think this is purely done because of tradition. A long time ago, we had
> tiny framebuffer drivers and most PCs did not have backlights, so it
> made sense to leave this optional.
>
> This was probably just always carried over.
>
> Arnd
>
okay. I think I will write a patch for nouveau then and send it out soonish
Powered by blists - more mailing lists