aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* kirkwood: use the generic uci-default functions for initial LED setupGabor Juhos2012-05-291-38/+4
| | | | SVN-Revision: 31994
* ramips: use the generic uci-default functions for initial LED setupGabor Juhos2012-05-291-41/+8
| | | | SVN-Revision: 31993
* ar71xx: use the generic uci-default functions for initial LED setupGabor Juhos2012-05-291-152/+60
| | | | SVN-Revision: 31992
* kirkwood: use uci-defaults to configure different boardsGabor Juhos2012-05-296-30/+107
| | | | | | Signed-off-by: Luka Perkov <openwrt@lukaperkov.net> SVN-Revision: 31990
* ramips: WAN LED for D-Link DIR-300-B1Gabor Juhos2012-05-292-0/+38
| | | | | | | | | | | | | | | | | | Add led devices for D-Link DIR-300-B1 WAN LED. Note that the GPIO state is also ANDed with the esw switch port 4 LED state, which is why I've set the amber LED to default-on. Closes: https://dev.openwrt.org/ticket/11326 Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de> [ juhosg: - fix comment style in mach-dir-300-revb.c, - remove the PPP specific LED setup, not everyone uses a PPP connection on the WAN interface] SVN-Revision: 31989
* ar71xx: do not override the mdio clock for ar9330. the override value ↵Felix Fietkau2012-05-281-2/+0
| | | | | | (obtained from an atheros driver) seems to break ethernet functionality SVN-Revision: 31956
* ar71xx: improve rx performance of the ethernet driver by using build_skb to ↵Felix Fietkau2012-05-282-41/+49
| | | | | | deliver a cache-hot skb to the network stack SVN-Revision: 31934
* ar71xx: fix MII clock settings for various chips, improves ethernet ↵Felix Fietkau2012-05-274-5/+30
| | | | | | stability on AR934x SVN-Revision: 31925
* kernel: fix suppressing -s for linking modules when profiling is enabledFelix Fietkau2012-05-271-1/+1
| | | | SVN-Revision: 31924
* ar71xx: fix TL-WR1041 image sizeGabor Juhos2012-05-271-1/+1
| | | | SVN-Revision: 31923
* ramips: rt3883: add device registration code for the SPI controllerGabor Juhos2012-05-272-0/+26
| | | | SVN-Revision: 31922
* ramips: allow to use the SPI driver on RT3662/RT3883Gabor Juhos2012-05-271-2/+2
| | | | SVN-Revision: 31921
* ramips: rt3883: fix GPIO reservation for the SPI pinsGabor Juhos2012-05-271-1/+1
| | | | SVN-Revision: 31920
* ramips: rt305x: remove superfluous controller_data assignmentGabor Juhos2012-05-271-1/+0
| | | | SVN-Revision: 31919
* ramips: make rt2x00 firmware extraction quietGabor Juhos2012-05-271-1/+1
| | | | SVN-Revision: 31918
* generic: rtl8367: rename a misnamed variableGabor Juhos2012-05-271-2/+2
| | | | SVN-Revision: 31917
* generic: rtl8366_smi: remove duplicated spinlock initializationGabor Juhos2012-05-271-2/+0
| | | | SVN-Revision: 31916
* generic: rtl8366_smi: rename debugfs Kconfig symbolGabor Juhos2012-05-275-17/+16
| | | | SVN-Revision: 31915
* generic: rtl8367: allow to use VLANs > 31Gabor Juhos2012-05-271-0/+3
| | | | SVN-Revision: 31914
* move files-3.3 -> filesJohn Crispin2012-05-2729-0/+0
| | | | SVN-Revision: 31912
* 3.2 R.I.P.John Crispin2012-05-27111-70773/+0
| | | | SVN-Revision: 31911
* dgn3500 support with eeprom loading from sysfsJohn Crispin2012-05-272-27/+197
| | | | | | | | | | | | | | | | | WIFI eeprom: As discussed, it is impossible for nand and spi flash platforms to have the eeprom data available from mtd. I suggested to load the eeprom from user-space. I've looked into regular firmware loading but this is only possible when using modules. I've created a sysfs entry that allows reading and writing the eeprom data to the platform data. After loading the eeprom data I rely on pci-hotplug support to disable the bogus pci device and rescan the bus (with fixups and all). Because hotplug is not available, an init script is created that performs the copy from mtd to platform data. I think it is best to eventually move the sysfs functions to dev_wifi_athxk.c file, this would get rid of the external to the ath9k platform data. SPI flash: It seems that the spi-xway driver is not really working. It causes my kernel to crash in all sorts of ways. I added to bitbang SPI to be able to the calibration data mention above. I've kept the original mtd partitioning that Netgear uses. Buttons/LED: Both buttons are working properly. Two leds are not enabled: The red internet led is connected to the pci_gnt1 pin... I can't disable it because then DMA stops working. The green wifi led is connected to an unknown atheros gpio. Signed-off-by: Pieter Voorthuijsen <p.voorthuijsen at gmail.com> SVN-Revision: 31910
* fixes zyxel p2601hnfxJohn Crispin2012-05-271-26/+35
| | | | | | | | | moves the linux partition, removes the config partition and the buttons settings have small adjustments. Signed-off-by: Luka Perkov <openwrt@lukaperkov.net> SVN-Revision: 31909
* Add basic configuration for new board ZTE H201L. Still missing are button ↵John Crispin2012-05-277-3/+125
| | | | | | | | and led gpio values. Signed-off-by: Luka Perkov <openwrt@lukaperkov.net> SVN-Revision: 31908
* kernel: properly pad the allocated headroom in skb_cow to NET_SKB_PADFelix Fietkau2012-05-271-1/+2
| | | | SVN-Revision: 31906
* linux/3.2: R.I.P.Gabor Juhos2012-05-27141-70858/+0
| | | | SVN-Revision: 31905
* xburst: remove support for old kernelsGabor Juhos2012-05-2754-24727/+0
| | | | SVN-Revision: 31904
* xburst: switch to 3.3 and add broken flagGabor Juhos2012-05-271-2/+2
| | | | SVN-Revision: 31903
* xburst: add support for 3.3Gabor Juhos2012-05-2726-0/+5408
| | | | SVN-Revision: 31902
* ppc44x: remove 3.2 supportGabor Juhos2012-05-273-264/+0
| | | | SVN-Revision: 31901
* ppx44x: switch to 3.3 and add broken flagGabor Juhos2012-05-271-2/+2
| | | | SVN-Revision: 31900
* ppc44x: add support for 3.3Gabor Juhos2012-05-273-0/+285
| | | | | | Compile tested only. SVN-Revision: 31899
* cobalt: switch to 3.3 and add broken flagGabor Juhos2012-05-272-6/+8
| | | | | | Compile tested only. SVN-Revision: 31898
* ep93xx: remove 3.2 supportGabor Juhos2012-05-274-1521/+0
| | | | SVN-Revision: 31897
* ep93xx: switch to 3.3 and add broken flagGabor Juhos2012-05-271-2/+2
| | | | SVN-Revision: 31896
* ep93xx: add support for 3.3Gabor Juhos2012-05-274-0/+1529
| | | | | | Compile tested only. SVN-Revision: 31895
* au1000: remove 3.2 supportGabor Juhos2012-05-274-312/+0
| | | | SVN-Revision: 31894
* au1000: switch to 3.3 and add broken flagGabor Juhos2012-05-271-2/+2
| | | | SVN-Revision: 31893
* au1000: add support for 3.3Gabor Juhos2012-05-274-0/+299
| | | | | | Compile tested only. SVN-Revision: 31892
* linux/3.1: R.I.P.Gabor Juhos2012-05-27128-71377/+0
| | | | SVN-Revision: 31891
* omap24xx: remove 3.1 supportGabor Juhos2012-05-2725-15609/+0
| | | | SVN-Revision: 31890
* omap24xx: switch to 3.3 and add broken flagGabor Juhos2012-05-271-2/+2
| | | | SVN-Revision: 31889
* cns3xxx: remove 3.1 supportGabor Juhos2012-05-2715-27496/+0
| | | | SVN-Revision: 31888
* cns3xxx: switch to 3.3 and add broken flagGabor Juhos2012-05-271-2/+2
| | | | SVN-Revision: 31887
* kernel: add a few patches for avoiding unnecessary skb reallocations - ↵Felix Fietkau2012-05-273-0/+59
| | | | | | significantly improves ethernet<->wireless performance with mac80211 based drivers SVN-Revision: 31886
* bcm63xx: build images for DSL-274XB revision F1Jonas Gorski2012-05-271-0/+3
| | | | | | | | | | | Build images for D-Link DSL-274XB revision F1. Flashing through original web UI as well as CFE works. Known issues: * wifi led inverted (on when wifi is off and vice cersa) * same issues as generic bcm6328 support SVN-Revision: 31885
* bcm63xx: add ath9k to atheros wifi profileJonas Gorski2012-05-271-1/+1
| | | | SVN-Revision: 31884
* bcm63xx: enable bcm6328 support and required driversJonas Gorski2012-05-271-3/+6
| | | | | | | | | | | BCM6328 support is in a usable state, with the following issues * internal switch port not configurable * external phys not supported * broadcom wifis will probably not work correctly * and all other generic bcm63xx issues (so yes, still no ADSL) SVN-Revision: 31883
* bcm63xx: add support for DSL-274XB rev F1Jonas Gorski2012-05-278-6/+146
| | | | SVN-Revision: 31882
* bcm63xx: fix port state after network downJonas Gorski2012-05-271-0/+28
| | | | | | | | bcm_enetsw_probe did not properly reset port states, resulting in connected ports staying disabled after bringing up the interface the second time. SVN-Revision: 31881
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 23:46:20 +0000