Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default
- To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>, 825026@bugs.debian.org
- Cc: Ben Hutchings <ben@decadent.org.uk>
- Subject: Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Sun, 9 May 2021 21:38:27 +0200
- Message-id: <[🔎] YJg6M3eUBDogZ6Jf@eldamar.lan>
- Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 825026@bugs.debian.org
- In-reply-to: <20160522194238.GA26059@sesse.net>
- References: <146393058849.4509.2087094899160344376.reportbug@soldroid> <1463942975.26238.43.camel@decadent.org.uk> <20160522190137.GA31245@sesse.net> <1463944218.26238.49.camel@decadent.org.uk> <20160522194238.GA26059@sesse.net> <146393058849.4509.2087094899160344376.reportbug@soldroid>
Control: tags -1 + moreinfo
Hi Steiner,
On Sun, May 22, 2016 at 09:42:38PM +0200, Steinar H. Gunderson wrote:
> On Sun, May 22, 2016 at 08:10:18PM +0100, Ben Hutchings wrote:
> > We build in code because we have to, not because it's merely useful.
> > And here we're talking about modules that are useful for only a small
> > proportion of armhf systems.
>
> Well, if you count number of device trees, it's about 110 devices out of
> 741 (having heartbeat or default-on as policy). So it's a minority (at least
> if you don't try to weight by number of sold devices, which would be much
> harder), but not complete obscurity.
>
> Anyways, I'm not going to try to drive this; my ARM bug reports are already
> being met with deafening silence on the Exynos list, so there's enough
> frustration involved :-) It's far from the most important thing in the big
> picture.
Despite the above involved frustration, do you know if someone else
did report the problem and/or you know the issue is not present
anymore with a recent kernel (from unstable ideally or mainline)?
Regards,
Salvatore
Reply to: