Modify

Opened 2 years ago

Last modified 2 years ago

#21825 reopened defect

mvebu build for wrt1900acv1 issue

Reported by: anomeome Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:

Description

RE: the non-functioning leds on wrt1900acv1 with DD/4.4 kernel.
Using this patch:
https://patchwork.ozlabs.org/patch/562162/

Still requires that you manually edit target/linux/generic/config-4.4 to set
CONFIG_LEDS_TLC591XX=y
And the build does not package the generated leds-tlc591xx.ko into the image file, so you have to take it to your device manually.

Attachments (0)

Change History (7)

comment:1 Changed 2 years ago by anonymous

It's been fixed in r48684: /changeset/48684.html

comment:2 Changed 2 years ago by anomeome

Fixed by r48684

comment:3 Changed 2 years ago by jow

  • Resolution set to fixed
  • Status changed from new to closed

comment:4 Changed 2 years ago by anonymous

  • Resolution fixed deleted
  • Status changed from closed to reopened

r48684 is a wrong fix to wrt1900ac-v1 led chip, the led kernel module get upstreamed from linux 4.3, but mvebu uses linux 4.1 by default for now, we should keep the previous leds-tlc59116 before migrating to linux 4.4.1 or other longterm versions. Add back tlc59116 and mark it only depends on linux 4.1 and older should be a real fix to this issue.

BTW, r48725 is the workaround to "fix" r48684, it can be reverted as well.

comment:5 Changed 2 years ago by anonymous

This is a real issue, the only thing in /sys/class/leds after flashing latest trunk yesterday (48736) is mamba:white:power

comment:6 Changed 2 years ago by mrfrezee

As it been fixed in recent trunk releases ?

comment:7 Changed 2 years ago by anonymous

r48808

I confirm that if you don't build with 4.4.1 kernel version, leds does not work.
So default build, without any modification of the mvebu Makefile, is broken.

Rgds

Add Comment

Modify Ticket

Action
as reopened .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.