On my HP dv2815 laptop, the total length of the triggers for my b43legacy
wireless device exceeds the maximum value of 50 defined in
include/linux/leds.h. As a result, the list is garbled.
Signed-off-by: Larry Finger <[email protected]>
---
Richard,
This is 2.6.31 material.
Larry
---
Index: wireless-testing/include/linux/leds.h
===================================================================
--- wireless-testing.orig/include/linux/leds.h
+++ wireless-testing/include/linux/leds.h
@@ -74,7 +74,7 @@ extern void led_classdev_resume(struct l
*/
#ifdef CONFIG_LEDS_TRIGGERS
-#define TRIG_NAME_MAX 50
+#define TRIG_NAME_MAX 70
struct led_trigger {
/* Trigger Properties */
Larry Finger wrote:
> On my HP dv2815 laptop, the total length of the triggers for my b43legacy
> wireless device exceeds the maximum value of 50 defined in
> include/linux/leds.h. As a result, the list is garbled.
>
> Signed-off-by: Larry Finger <[email protected]>
> ---
Richard,
Please drop this. That length change is a red herring. Something is corrupting
the list of triggers, but this length is not it.
Sorry for the noise.
Larry
On Thu, 2009-04-02 at 17:06 -0500, Larry Finger wrote:
> Larry Finger wrote:
> > On my HP dv2815 laptop, the total length of the triggers for my b43legacy
> > wireless device exceeds the maximum value of 50 defined in
> > include/linux/leds.h. As a result, the list is garbled.
> >
> > Signed-off-by: Larry Finger <[email protected]>
> > ---
>
> Richard,
>
> Please drop this. That length change is a red herring. Something is corrupting
> the list of triggers, but this length is not it.
>
> Sorry for the noise.
I was about to raise some concerns about this patch as its just hiding
some underlying memory corruption. I don't think this is related to the
LED code but let me know if it turns out to be.
Cheers,
Richard
--
Richard Purdie
Intel Open Source Technology Centre