mr/openwrt
2
0
Fork 1
Code Issues 7 Pull Requests Releases Wiki Activity
34,580 Commits 3 Branches 0 Tags 517 MiB
C 90.8%
Makefile 4.4%
Shell 1.6%
Roff 1.5%
Perl 0.6%
Other 1%
b529387d8c
Go to file
blogic b529387d8c lantiq: use the same functionality for all ethernet phys led 
The VGV7510KW22 has the leds for LAN1-3 connected to pin1 of the phys
and the led for LAN4 connect to pin0 of the phy. This results with the
current configuration in a fast flashing LAN4 led as soon as a network
cable is connected. Something similar was reported on the forum[1] for
the VGV7519 as well.

Since it isn't predicable to which pin a (single) phy led is connected,
use the (default) pin1 functionality

    Constant On: 10/100/1000MBit
    Blink Fast: None
    Blink Slow: None
    Pulse: TX/RX

for all ethernet phy leds.

After checking pictures of all vr9 boards, it looks like only the VG3503J
has more than one led connected per phy. Using the phy led device tree
bindings to assign the functionality to the "additional" leds, the
VG3503J phy leds should behave as before.

Signed-off-by: Mathias Kresin <openwrt@kresin.me>

[1] https://forum.openwrt.org/viewtopic.php?pid=321523

SVN-Revision: 49270
2016-05-10 10:43:12 +02:00
config global: introduce ALL_NONSHARED symbol 2016-04-13 17:24:12 +02:00
docs build: Prevent more gzip timestamps 2015-07-14 09:57:45 +00:00
include build: add support for specifying extra package dependencies for prepared, configured and built 2016-05-05 19:43:23 +01:00
package ncurses: install pkg-config files to fix util-linux build breakage 2016-05-10 10:12:01 +02:00
scripts metadata.pl: add support for selecting packages available only via PROVIDES 2016-05-09 14:48:49 +02:00
target lantiq: use the same functionality for all ethernet phys led 2016-05-10 10:43:12 +02:00
toolchain toolchain: gcc: fix build with GCC 6 2016-05-08 23:37:40 +02:00
tools tools: mkimage: sync include/linux/compiler*.h with u-boot master 2016-05-08 23:37:40 +02:00
.gitattributes add .gitattributes to prevent the git autocrlf option from messing with CRLF/LF in files 2012-05-08 13:30:49 +00:00
.gitignore build: add integration for managing opkg package feed keys 2015-04-06 19:39:51 +00:00
BSDmakefile add missing copyright header 2007-02-26 01:05:09 +00:00
Config.in branding: add LEDE branding 2016-03-24 22:40:13 +01:00
feeds.conf.default feeds.conf.default: remove the commented ancient feeds 2016-04-20 17:19:08 +00:00
LICENSE finally move buildroot-ng to trunk 2016-03-20 17:29:15 +01:00
Makefile branding: add LEDE branding 2016-03-24 22:40:13 +01:00
README branding: add LEDE branding 2016-03-24 22:40:13 +01:00
rules.mk rules.mk: introduce new variable OUTPUT_DIR 2016-04-06 21:49:15 +02:00

README 

This is the buildsystem for the LEDE Linux distribution.

Please use "make menuconfig" to configure your appreciated
configuration for the toolchain and firmware.

You need to have installed gcc, binutils, bzip2, flex, python, perl, make,
find, grep, diff, unzip, gawk, getopt, subversion, libz-dev and libc headers.

Run "./scripts/feeds update -a" to get all the latest package definitions
defined in feeds.conf / feeds.conf.default respectively
and "./scripts/feeds install -a" to install symlinks of all of them into
package/feeds/.

Use "make menuconfig" to configure your image.

Simply running "make" will build your firmware.
It will download all sources, build the cross-compile toolchain, 
the kernel and all choosen applications.

You can use "scripts/flashing/flash.sh" for remotely updating your embedded
system via tftp.

The LEDE system is documented in docs/. You will need a LaTeX distribution
and the tex4ht package to build the documentation. Type "make -C docs/" to build it.

To build your own firmware you need to have access to a Linux, BSD or MacOSX system
(case-sensitive filesystem required). Cygwin will not be supported because of
the lack of case sensitiveness in the file system.


Sunshine!
	Your LEDE Community
	http://www.lede-project.org