| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 48223
|
|
|
|
|
|
|
|
| |
linux 4.4 (since commit 08b3c894e56580b8ed3e601212a25bda974c3cc2
"MIPS: lantiq: Disable xbar fpi burst mode") requires that the xbar is
defined in the .dts of vrx200 (VR9) SoCs.
SVN-Revision: 48056
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48047
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48046
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48045
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48044
|
|
|
|
|
|
|
|
|
|
| |
The P2812HNU-F3 doesn't have usb leds. Only the P2812HNU-F1 has those
leds.
Reported-by: Sylwester Petela <sscapi@gmail.com>
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48043
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The leds of the following boards are not renamed due to lack of
manuals/informations:
- ARV7519PW
- ARV7510PW22
- ARV4510PW
The leds of the ARV4518PWR01* boards are unchanged, since the leds doesn't
match the leds from the manual or pictures (e.g. there shouldn't be a wps led).
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48042
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The BTHOMEHUBV5A has a RGB power led, where every colour is perfect to
indicate the current boot state. This patch adds support for such cases.
The existing led sequences should be the same as before.
Boards which are using a led different from power (like TDW89x0) are
changed to switch of the led after boot
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48041
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dsl_control (dsl_notify.sh) is the only process which is aware of the
state of the atm/ptm interface. Use the dsl led exclusive for the dsl
line state.
On boards which don't have a distinct internet and a dsl led, let the
netdev status of the atm interface trigger the shared led.
Triggering the shared led according to the status of the ppp interface
isn't suitable, since the led would be switched of if the ppp
connection goes down, but the line is still in sync.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48040
|
|
|
|
|
|
|
|
| |
Use the power leds defined in the dts file instead of hardcoded led names.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48039
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove all now double defined leds from the led board file. Use pppoe
as default for all broadband connections, since it's the default in
OpenWrt now.
Rename the the wifi leds to make sure, the not applicable default
values get overwritten.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48038
|
|
|
|
|
|
|
|
|
|
| |
- ARV7525PW: use the power led as dsl led as done by the stock firmware
- FRITZ3370: use the info led as internet led
- FRITZ7320: use the power led as dsl led as done by the stock firmware
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48037
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the same led logic and labels as the OEM firmware (red = okay,
blue = failure).
Add the red internet led.
Remove missing usb led workaround. The workaround shouldn't be in the
default configuration.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48036
|
|
|
|
|
|
|
|
|
|
|
| |
No need to switch (and keep) on all leds at boot. Use the same led
logic and labels as the OEM firmware (red = okay, blue = failure).
Add the red internet led.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48035
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48034
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48033
|
|
|
|
|
|
|
|
| |
The workaround shouldn't be in the default configuration.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48032
|
|
|
|
|
|
|
|
| |
Beside the used labels, they are the same on both boards.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48031
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48002
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's not necessary to define PCI_* if pci_ids.h is included a few
lines above.
The change to pci_ids.h doesn't look intentional to me, especially
since the former value is added to the top of ifxmips_fixup_pcie.c.
Both changes were introduced with the kernel 4.1 support patches and
were not present in the 3.18 patches.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 47996
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the same max spi frequency as set in u-boot.
According to the datasheets, the Q64-104HIP as well as the Winbond
25Q64FVSIG support spi frequencies up to 50 MHz. During my tests, the
Q64-104HIP couldn't be recognized/initialized if the frequency
was > 40MHz.
Both chips do support fast read as well.
While touching the dts file, I fixed the dtc compiler warnings.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 47994
|
|
|
|
|
|
|
|
|
| |
using the special tag in this way lead to port mirroring for certain types of traffic.
fallback to using th PMAC_EWAN register for the wan portmap.
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 47993
|
|
|
|
|
|
|
|
|
| |
This patch configures the correct ath9k WLAN LED polarity for the TDW8970,
and for the TDW8980 as well.
Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
SVN-Revision: 47969
|
|
|
|
|
|
| |
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
SVN-Revision: 47918
|
|
|
|
|
|
|
|
|
| |
Still unused, but u-boot doesn't take care of the led, which results in a
permanent switched on 5GHz LED.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 47915
|
|
|
|
|
|
|
|
|
|
| |
- Use common OpenWrt blink patterns instead of custom ones
- Add preinit_regular hook
- Handle the TDW89X0 that does not have a configurable power LED
Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
SVN-Revision: 47914
|
|
|
|
|
|
|
|
| |
This patch configures the correct ath9k WLAN LED polarity for the TDW8970.
Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
SVN-Revision: 47913
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The TDW8970 has a AR9381, which is the bgn 3x3:3 variant of the AR938x family.
The TDW8980 has a AR9287, which is the bgn 2x2:2 variant of the AR928x family.
This means that the chip for both routers is 2.4 GHz only.
Anyway, the manufacturer didn't disable the 5 GHz band in the EEPROM partition
(at least on my TDW8970).
So this patch disables the 5 GHz band.
Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
SVN-Revision: 47912
|
|
|
|
|
|
|
|
| |
the device tree.
Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
SVN-Revision: 47911
|
|
|
|
|
|
|
|
|
| |
Replace former uci-defaults.sh implementation with the uci-defaults-new.sh one
and update all users accordingly.
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
SVN-Revision: 47867
|
|
|
|
|
|
|
|
|
| |
Because of dsl-vrx200-firmware-xdsl-* there's no need anymore to
download a dsl firmware at runtime.
Signed-off-by: Andre Heider <a.heider@gmail.com>
SVN-Revision: 47851
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The switch to uci-defaults-new.sh revealed a bug in the former used
uci-defaults.sh, which failed to add leds with colons in the led name.
This bug isn't any longer present in uci-defaults-new.sh and therefore
all via DT defined leds will be added to /etc/config/system with their initial
on/off state, regardless whether they are already added by the board specific
led mappings.
This results for a BTHOMEHUBV5A into the following led configuration:
- soc:blue:power is added as led_power with the initial state "switched on"
- soc:blue:power is added as led_soc_blue_power with the initial state "switched off"
With the final result of a switched off power led after boot.
The only led that needs to be added is the BTHOMEHUBV5A specific dimmed led.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 47850
|
|
|
|
|
|
|
|
|
|
|
| |
Starting with r47755 the pppoe wan interface section isn't any longer added to
the network config on firstboot, using the default configuration. Since the
commit message does not mention such a change, I assume that this wasn't
intentionally.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 47793
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 47785
|
|
|
|
|
|
|
|
|
| |
Now that we have redistributable vdsl/adsl firmware blobs in /lib/firmware,
we can drop the dsl_fw partition and extend the firmware partition.
Signed-off-by: Andre Heider <a.heider@gmail.com>
SVN-Revision: 47783
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47774
|
|
|
|
|
|
|
|
| |
(and subsequent timeouts)
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47770
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47768
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47767
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47766
|
|
|
|
|
|
|
|
| |
loading vr9 drivers
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47764
|
|
|
|
|
|
| |
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
SVN-Revision: 47755
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47690
|
|
|
|
|
|
|
|
| |
This fixes a problem introduced in r47624.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 47628
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47624
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds the posibility to config the led behaviour of the lantiq phys
over the devicetree bindings.It patches the 0023-NET-PHY-adds-driver-for-lantiq-PHY11G
for 3.18 and 4.1. I have also added a register description overview for
applicable values. This goes to the documentation folder in the linux kernel.
Signed-off-by: Florian Eckert <Eckert.Florian@googlemail.com>
SVN-Revision: 47566
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch improves the default configuration of DWC2 on lantiq SoCs
somewhat:
* Set maximum packet count to largest allowed value by the DWC2 (511)
* Use 16-bit DMA bursts
* Divide fifo buffers more evenly
Default fifo buffer sizes from original ltq-hcd driver seem really
irrational. For example according to DWC2 data book rxfifo size of 240
will not fit even a single full length USB packet. On the other hand
non-periodic tx fifo size of 240 is more than enough to fit one complete
packet.
Change the sizes around to improve the situation and to fix some issues
especially with isochronous USB transfers.
Signed-off-by: Antti Seppälä <a.seppala@gmail.com>
SVN-Revision: 47563
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a basic implementation of clk_round_rate()
The clk_round_rate() function is called by multiple drivers and
subsystems now and the lantiq clk driver is supposed to export this,
but doesn't do so, this causes linking problems like this one:
ERROR: "clk_round_rate" [drivers/media/v4l2-core/videodev.ko] undefined!
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 47254
|
|
|
|
|
|
|
|
| |
https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.1.11
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 47252
|