[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190429181245.GA24658@amd>
Date: Mon, 29 Apr 2019 20:12:45 +0200
From: Pavel Machek <pavel@....cz>
To: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
Cc: Marek Behun <marek.behun@....cz>,
Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-leds@...r.kernel.org
Subject: Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia)
On Mon 2019-04-29 19:51:40, Enrico Weigelt, metux IT consult wrote:
> On 29.04.19 18:53, Pavel Machek wrote:
> >>> Theoretically. But we both now that probability of that is very low,
> >>> and that likely driver would need other updates, too... right?
> >>
> >> What would be the benefit to add ARM dependency? So that distro
> >> compilations don't ship the turris_omnia driver unnecesarily?
> >
> > That, and so that people are not asked "do you want to enable omnia
> > LEDs?" when they update their kernel on i386.
>
> Is that controller only built-in into some SoCs, or also available
> as a separate chip ?
AFAIU.. separate chip, but runs firmware not likely to be available
outside Turris routers.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists