Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2022-02-27 Thread Diederik de Haas
Control: fixed -1 5.15-1~exp1 On Sun, 22 May 2016 17:23:08 +0200 "Steinar H. Gunderson" wrote: > Package: src:linux > Version: 4.5.3-2 > > My ODROID XU4 has a blue LED on it, which, after #824941 has been fixed, > is supposed to be a heartbeat LED, being solid-on during the bootloader > and

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2021-05-09 Thread Salvatore Bonaccorso
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

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
On Sun, May 22, 2016 at 09:42:38PM +0200, Steinar H. Gunderson wrote: > 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

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
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

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Ben Hutchings
On Sun, 2016-05-22 at 21:01 +0200, Steinar H. Gunderson wrote: > On Sun, May 22, 2016 at 07:49:35PM +0100, Ben Hutchings wrote: > > > > The device tree already tells the kernel what trigger should be used, > > and the kernel can then make the decision whether that requires loading > > a module. >

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
On Sun, May 22, 2016 at 07:49:35PM +0100, Ben Hutchings wrote: > The device tree already tells the kernel what trigger should be used, > and the kernel can then make the decision whether that requires loading > a module. Does this mean the initramfs would also need to know that the module should

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Ben Hutchings
Control: tag -1 upstream On Sun, 2016-05-22 at 17:23 +0200, Steinar H. Gunderson wrote: > Package: src:linux > Version: 4.5.3-2 > Severity: normal > > Hi, > > My ODROID XU4 has a blue LED on it, which, after # has been fixed, > is supposed to be a heartbeat LED, being solid-on during the

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
On Sun, May 22, 2016 at 05:23:08PM +0200, Steinar H. Gunderson wrote: > My ODROID XU4 has a blue LED on it, which, after # has been fixed, I meant #824941. /* Steinar */ -- Homepage: https://www.sesse.net/

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
Package: src:linux Version: 4.5.3-2 Severity: normal Hi, My ODROID XU4 has a blue LED on it, which, after # has been fixed, is supposed to be a heartbeat LED, being solid-on during the bootloader and then flashing when the OS is active. (The manual says so, and “heartbeat” is the default mapping