| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 48024
|
|
|
|
|
|
| |
Signed-off-by: Bjoern Dobe <bjoern@dobecom.de>
SVN-Revision: 48022
|
|
|
|
|
|
|
| |
Signed-off-by: Bjoern Dobe <bjoern@dobecom.de>
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 48021
|
|
|
|
|
|
| |
Signed-off-by: Bjoern Dobe <bjoern@dobecom.de>
SVN-Revision: 48020
|
|
|
|
|
|
| |
Signed-off-by: Bjoern Dobe <bjoern@dobecom.de>
SVN-Revision: 48019
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the name of the .ubi produced to strip out the word 'factory'. This is
mainly due to the fact that there is no difference between the Ventana 'factory'
image vs the standard image.
Name changes from:
openwrt-imx6-ventana-squashfs.nand-factory_<size>.ubi to
openwrt-imx6-ventana-squashfs-nand_<size>.ubi
Signed-off-by: Pushpal Sidhu <psidhu@gateworks.com>
SVN-Revision: 48016
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some Ventana boards have a Marvell sky2 GigE controller as eth1 however
assigning the mac address through device-tree is difficult because the
PCI slot can move around depending on board configuration and slot population.
To work around this we add a patch to the sky2 driver to allow accessing its
mac address via a device-tree alias.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
Signed-off-by: Pushpal Sidhu <psidhu@gateworks.com>
SVN-Revision: 48013
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Ventana boards the Gateworks System Controller is the only device on I2C1
(/dev/i2c-0) and it can NAK transfers if it is busy in an ADC loop. Because
this is a multi-function device with several slave addresses it is best to
add retries at the controller level instead of within each slave driver. This
adds a patch that adds 3 retries for i2c transactions only for Ventana boards
and only for I2C1
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
Signed-off-by: Pushpal Sidhu <psidhu@gateworks.com>
SVN-Revision: 48012
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a backport of a2291badc355d58ead5c19ae0609468947416040 from thermal-soc
accepted upstream.
The IMX6Q/IMX6DL SoC's have a 2-bit temperature grade stored in OTP. Instead
of assuming 85C for passive cooling threshold and 100C for critical base
these thresholds off the thermal gade max CPU temperature:
- passive threshold: max - 10C
- critical threshold: max - 5C
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 48011
|
|
|
|
|
|
|
|
| |
Upstream status: Accepted
Signed-off-by: Pushpal Sidhu <psidhu@gateworks.com>
SVN-Revision: 48010
|
|
|
|
|
|
|
|
|
|
| |
Certain board revisions of the GW52xx support an SPI host controller with
a single chip-select going to an off board connector.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
Signed-off-by: Pushpal Sidhu <psidhu@gateworks.com>
SVN-Revision: 48009
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Build and boot tested on the following hardware:
* GW54xx
* GW53xx
* GW52xx
* GW51xx
* GW552x
* GW551x
Signed-off-by: Pushpal Sidhu <psidhu@gateworks.com>
SVN-Revision: 48008
|
|
|
|
|
|
|
|
| |
Since 3.18 kernel support was dropped, remove lingering files.
Signed-off-by: Pushpal Sidhu <psidhu@gateworks.com>
SVN-Revision: 48007
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 48005
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48002
|
|
|
|
|
|
|
|
|
| |
As explained earlier, using SWITCH_TYPE_LINK gives more flexibility,
it doesn't require e.g. string parsing to read some data.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 47999
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far we were sending link data as a string. It got some drawbacks:
1) Didn't allow writing clean user space apps reading link state. It was
needed to do some screen scraping.
2) Forced whole PORT_LINK communication to be string based. Adding
support for *setting* port link required passing string and parting
it in the kernel space.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 47997
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Previously switching to non-existing device (interface) could result in
leaving LED on.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 47990
|
|
|
|
|
|
|
|
|
|
| |
We may just delete timer on every trigger update and then start it again
if needed. This will let us avoid both: races and locking in frequently
called timer callback.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 47987
|
|
|
|
|
|
|
|
|
|
| |
Read/write lock was adding useless complexity, there wasn't any real
gain in case of this driver.
Also switch to _bh variants to avoid deadlocks.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 47986
|
|
|
|
|
|
| |
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
SVN-Revision: 47985
|
|
|
|
|
|
| |
Signed-off-by: Roman Yeryomin <roman@advem.lv>
SVN-Revision: 47983
|
|
|
|
|
|
| |
Signed-off-by: Roman Yeryomin <roman@advem.lv>
SVN-Revision: 47982
|
|
|
|
|
|
|
|
|
|
|
| |
- separate qca956x and tp9343 (they use different IDs)
- rename qca9561->qca956x for consistency
- add missing bits (device reset, gpio output select)
- fix wmac setup
Signed-off-by: Roman Yeryomin <roman@advem.lv>
SVN-Revision: 47981
|
|
|
|
|
|
|
|
| |
This patch is to add support for the AirTight Networks C-55 Access Point
Signed-off-by: Chris R Blake <chrisrblake93@gmail.com>
SVN-Revision: 47973
|
|
|
|
|
|
| |
Signed-off-by: Roman Yeryomin <roman@advem.lv>
SVN-Revision: 47972
|
|
|
|
|
|
| |
Signed-off-by: Roman Yeryomin <roman@advem.lv>
SVN-Revision: 47971
|
|
|
|
|
|
|
|
|
| |
4.1 got little bit larger than 4MB and I couldn't get lzma loader
working on this platform
Signed-off-by: Roman Yeryomin <roman@advem.lv>
SVN-Revision: 47970
|
|
|
|
|
|
|
|
|
| |
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: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47966
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47963
|
|
|
|
|
|
|
|
|
|
| |
All supported kernels require patching ledtrig-netdev in the same way,
so it's safe to just move these changes to the base version of this
driver. We needed these patches for some old kernels 2.6.36 and 3.11.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 47962
|
|
|
|
|
|
| |
Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
SVN-Revision: 47957
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In r45970 the MAC swap handling was made opt-in, however some boards
have been forgotten during the conversion. Since the reference design
uses this MAC swapping, and pretty much all known boards using this chip
seem to do so too, enabling the swapping is a more reasonable default
than leaving it disabled.
Change the code to still allow boards to opt-out of this.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47956
|
|
|
|
|
|
|
|
|
|
| |
The following patch is to add ath79_register_m25p80_large, which sets
is_flash to false to support bit banging. This is needed on some 32MB+
SPI chips, such as the S25FL256S1
Signed-off-by: Chris R Blake <chrisrblake93@gmail.com>
SVN-Revision: 47952
|
|
|
|
|
|
|
|
|
|
| |
The MR18 stores the ath9k eeprom values on the NAND.
This patch makes it possible to retrieve the images
from there.
Signed-off-by: Chris R Blake <chrisrblake93@gmail.com>
SVN-Revision: 47948
|
|
|
|
|
|
|
|
|
| |
move all library includes and 'firmware already exists'
check to the top of the script.
Signed-off-by: Chris R Blake <chrisrblake93@gmail.com>
SVN-Revision: 47947
|
|
|
|
|
|
|
|
|
|
|
|
| |
OpenWrt configuration part of support for the PowerCloud Systems
CR5000. The CR5000 is a dual-band 802.11n wireless router with
8MB flash, 64MB RAM, (unused on stock firmware) USB 2.0 port and
five port gigabit ethernet switch. The CR5000 was sold as
hardware for the Skydog cloud-managed router service.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47946
|
|
|
|
|
|
|
|
|
|
|
|
| |
OpenWRt configuration part of support for the PowerCloud
Systems CR3000. The CR3000 is a 802.11n 2.4 GHz wireless router with
8MB flash, 64MB RAM, a four port gigabit ethernet switch, and a fast
ethernet wan port that was sold by PowerCloud Systems as
hardware for the Skydog cloud-managed router service.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47945
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Openwrt configuration part of support for PowerCloud CAP324
Cloud AP. The CAP324 Cloud AP is a device sold by PowerCloud Systems
who's stock firmware (CloudCommand) provides 'cloud' based managment
of large numbers access points.
The CAP324 is a dual-band 802.11n wireless access point with 16MB flash
and 128MB RAM and single gigabit ethernet port. It can be powered via PoE
or a wall wart.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47944
|
|
|
|
|
|
|
|
|
|
|
|
| |
Kernel part of support for the PowerCloud Systems CR5000. The
CR5000 is a dual-band 802.11n wireless router with 8MB flash,
64 MB RAM, (unused in stock firmware) USB 2.0 port, and five
port gigabit ethernet switch. The CR5000 was sold as hardware for
the Skydog cloud-managed router service.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47943
|
|
|
|
|
|
|
|
|
|
|
|
| |
Image generation part of support for PowerCloud CR3000. The CR3000 is
a 802.11n 2.4 GHz wireless router with 8MB flash, 64MB RAM,
a four port fast ethernet switch, and a fast ethernet wan port which
was sold by PowerCloud Systems as hardware for the Skydog
cloud-managed router service.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47942
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Image generation (and mtd partition) part of support for
PowerCloud CAP324 Cloud AP. The CAP324 Cloud AP is a device sold by
PowerCloud Systems who's stock firmware (CloudCommand) provides
'cloud' based managment of large numbers of access points.
The CAP324 is a dual-band 802.11n wireless access point with 16MB flash
and 128MB RAM and single gigabit ethernet port. It can be powered via
PoE or a power adaptor.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47941
|
|
|
|
|
|
|
|
|
|
|
|
| |
Kernel part of support for the PowerCloud Systems CR5000. The
CR5000 is a dual-band 802.11n wireless router with 8MB flash,
64 MB RAM, (unused in stock firmware) USB 2.0 port, and five
port gigabit ethernet switch. The CR5000 was sold as hardware for
the Skydog cloud-managed router service.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47940
|
|
|
|
|
|
|
|
|
|
|
|
| |
Kernel part of support for PowerCloud CR3000. The CR3000 is
a 802.11n 2.4 GHz wireless router with 8MB flash, 64MB RAM,
a four port fast ethernet switch, and a fast ethernet wan port which
was sold by PowerCloud Systems as hardware for the Skydog
cloud-managed router service.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47939
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Kernel part of support for PowerCloud CAP324 Cloud AP.
The CAP324 Cloud AP was a device sold by PowerCloud Systems as hardware for
the CloudCommand service for 'cloud' based managment of large numbers
access points.
The CAP324 is a dual-band 802.11n wireless access point with 16MB flash
and 128MB RAM and single gigabit ethernet port. It can be powered via PoE
or a power adaptor.
Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com>
SVN-Revision: 47938
|
|
|
|
|
|
|
|
| |
Enable it from .dts files that need it, also remove redundant properties
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 47936
|