aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm47xx/base-files/etc
Commit message (Collapse)AuthorAgeFilesLines
* brcm47xx: fix switch port order for Netgear WN2500RP V1Walter Sonius2020-01-211-0/+5
| | | | | | | | | | | | | | The Netgear WN2500RP V1 switch0 already works for LAN however the port order for the LAN ports is inverted. Correct physical port order watched from the back of the device is: 4 / 3 / 2 / 1 WAN port is absent on this device and therefore removed from switch config. Signed-off-by: Walter Sonius <walterav1984@gmail.com> [move block to maintain alphabetic sorting] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 098cbc68ee23db589ed6f0d081fe26cc385462f2)
* brcm47xx: fix switch port order for Netgear WNR3500 V2Walter Sonius2020-01-211-0/+1
| | | | | | | | | | | | The Netgear WNR3500 V2 switch0 already works for WAN/LAN however the port order for the LAN ports is inverted. Correct physical port order watched from the back of the device is: Internet / 4 / 3 / 2 / 1 this resembles the Linksys E3000 V1. Verfied with imagebuilder edit FILES=/etc/board.d/01_network Signed-off-by: Walter Sonius <walterav1984@gmail.com> (cherry picked from commit cf2f1fc6871da0320afeefaa799af87fc7c0d1db)
* brcm47xx: add switch configuration for WNR3500LOlli Asikainen2019-12-111-1/+2
| | | | | | | | | | | | | | | | | | | | | Netgear WNR3500L is an already supported device, but out of the box, the device has no switch configuration and there is no wan. The correct configuration for this specific model is similar to some other models. This simple commit adds the correct switch and the out-of-the-box experience is improved. Experimentally determined: Port 0 => WAN Port 1..4 => LAN Port 5..7 => unused Port 8 => CPU Signed-off-by: Olli Asikainen <olli.asikainen@gmail.com> Tested-by: Fabian Zaremba <fabian@youremail.eu> [added port mapping to commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit deb835849aeb713968aaa48bf046101140ab4825)
* brcm47xx: fix switch port labels for Asus WL500GP V2Michael Heimpold2019-10-151-1/+5
| | | | | | | | The switch port naming in LuCI does not fit the physical numbers on the front of this device. Since this is confusing, fix it. Signed-off-by: Michael Heimpold <mhei@heimpold.de> (cherry picked from commit e56e5a454e729f1067ba1fc8acfc18b99ccb88b4)
* brcm47xx: cosmetic fix in model detectionPaul Wassi2018-08-131-1/+1
| | | | | | | | In "brcm47xx: rework model detection" the file 01_detect was moved to 01_network, therefore also update the warning message in case everything fails. Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* brcm47xx: rework model detectionJo-Philipp Wich2018-07-301-14/+17
| | | | | | | | | | | | | | | | | | | | | | | | | On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* brcm47xx: add switch port mapping to Asus WL-500WMirko Parthey2018-05-241-1/+1
| | | | | | | | | | | Switch ports 0..3 are connected to external ports LAN{1..4} in sequence, switch port 4 is not used, and switch port 5 is connected to the CPU. The WAN port is attached to the CPU's second network interface; it has no connection to the internal switch. Reuse the "Dell TrueMobile 2300" entry, which describes the same mapping. Signed-off-by: Mirko Parthey <mirko.parthey@web.de>
* brcm47xx: fix switch port mapping on D-Link DIR-330Antony Black2017-11-161-0/+1
| | | | | | | | D-Link DIR-330 is clone of ASUS WL500GP2, by default conf the WAN port is eth1, it's not working cus eth1 not soldered and wan port function performs 5th port of the switch. Signed-off-by: Antony Black <gtrtfm@gmail.com>
* brcm47xx: fix switch port mapping on Asus RT-N16Tim Thorpe2017-11-101-1/+1
| | | | | | | On the Asus RT-N16, the ports are not mapped the in the same way as the RT-N12. It is, however, the same as the Linksys E3000v1. Signed-off-by: Tim Thorpe <timfthorpe@gmail.com>
* brcm47xx: fix switch port mapping on Asus RT-N12 and RT-N16 modelsJo-Philipp Wich2017-07-211-0/+2
| | | | | | | | | | | | | On Asus RT-N12 and RT-N16 models, the WAN and LAN4 ports are swapped in the initial switch configuration since the presets present in nvram appear to be wrong. Add special casing for these models to detect_by_model() in order to ensure a proper switch configuration. Fixes FS#502. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* treewide: use only board_name function to get nameMathias Kresin2017-07-151-1/+1
| | | | | | | | | | | | Do not parse /tmp/sysinfo/board_name, /proc/cpuinfo or the device tree compatible string directly. Always use the board_name function to get the board name. The admswconfig package still reads /proc/cpuinfo directly. The code looks somehow broken and the whole adm5120 which uses this package looks unmaintained. Leave it as it is for now. Signed-off-by: Mathias Kresin <dev@kresin.me>
* brcm47xx: use DMZ LED as status indicatorMirko Parthey2017-07-021-15/+7
| | | | | | | | | | | | | On the Linksys WRT54GSv1, the Power LED flickers in the "off" state. Indicate status using the DMZ LED if available, since it has solid "on" and "off" states. This change was tested on the WRT54GSv1, but may also affect other brcm47xx devices. Fixes FS#793. Signed-off-by: Mirko Parthey <mirko.parthey@web.de>
* treewide: remove bad local shell variable declarationsJo-Philipp Wich2016-09-242-9/+9
| | | | | | | Local variable declarations outside of functions are illegal since the Busybox update to v1.25.0, therfore remove them from the appropriate places. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* brcm47xx: fix wgt634u port assignment, broken since openwrt r47866Russell Senior2016-05-101-1/+1
| | | | Signed-off-by: Russell Senior <russell@personaltelco.net>
* brcm47xx: add proper switch port mapping for WRT610Nv2 / Linksys E3000v1Jo-Philipp Wich2016-01-271-0/+5
| | | | | | Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 48511
* brcm47xx: fix switch config for devices with WAN port 0Rafał Miłecki2015-12-181-0/+14
| | | | | | | | | Commit r47866 dropped default values which were handling WAN interface at port 0. Fix it by handling 2 more cases on NVRAM values. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 47932
* all: drop old uci-defaults.shJo-Philipp Wich2015-12-111-1/+1
| | | | | | | | | 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
* brcm47xx: migrate network config to board detection frameworkJo-Philipp Wich2015-12-113-241/+173
| | | | | | Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
* add "preinit_regular" diag.sh set_state argumentJohn Crispin2014-12-151-0/+3
| | | | | | | | | | | | This new argument is used right after starting regular preinit (which happens if failsafe wasn't triggered). The main purpose of "preinit" argument is to indicate that failsafe can be triggered, however we were missing a way to inform user that we don't wait for a trigger anymore. With this change it's clear when failsafe mode can be triggered. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 43715
* brcm47xx: don't create named switch_vlan sectionsHauke Mehrtens2014-07-261-2/+0
| | | | | | | | | | | It doesn't seem to be used anywhere, it's incompatible with other targets and can be confusing. People may think they need to update section name every time they change VLAN ID (well, even I was doing that). Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 41835
* brcm47xx: fix special board handling for some devicesHauke Mehrtens2014-07-141-19/+7
| | | | | | | | | | | Some devices were renamed when converted from diag to in kernel board detection and it was not changed in netconfig. Devices not in the kernel board detection are removed now. This should close: #17111, #16968, #13202 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 41663
* brcm47xx: get switch name from swconfig firstHauke Mehrtens2014-07-051-3/+5
| | | | | | | | | Without this patch the switch config for the adm switch did not worked, because hey are not names eth0. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 41512
* brcm47xx: migrate basic network settings from old releasesHauke Mehrtens2014-07-031-0/+29
| | | | | | | | | | | | | | | | Old OpenWrt releases were using network configs that are not valid anymore. They were specifying ports tagging in a different way (or were not tagging CPU at all) and were using VID 0 which is a reserved value. Modifying network configuration to apply all needed changes would be pretty tricky. Script /etc/init.d/netconfig that generates new config is quite complex itself. So instead let's save the most important settings, regenerate config from the scratch and restore values. This should work for 99% of users. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 41500
* bcm47xx: use eth0 for switch nameHauke Mehrtens2014-06-071-3/+3
| | | | | | | | | | | This fixes some strange problems with tg3. I assume that the Ethernet driver was not brought up if the switch was named switch0. This was reported and tested by ernesto (Faulp3lz). Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 41042
* brcm47xx: parse model from cpuinfoHauke Mehrtens2014-01-121-3/+2
| | | | | | | | | Instead of looking into the proc entry provided by broadcom-diag use the board info from /proc/cpuinfo to get the board we are on. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 39256
* brcm47xx: fix led indicationHauke Mehrtens2014-01-121-16/+26
| | | | | | | | | Use the new led api also on brcm47xx. The led for failsafe indication is searched for. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 39255
* brcm47xx: use "firmware" partition nameHauke Mehrtens2013-12-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Some time ago, after switching to the mainline bcm47xxpart driver following patch has been applied: commit 03cef8725d2062335ffc3de50fc037b294fd458c Author: hauke <hauke@3c298f89-4303-0410-b956-a3cf2f4a3e73> Date: Sat Apr 6 22:22:26 2013 +0000 brcm47xx: use old partition names again for kernel 3.8 This fixes sysupgrade. The partition names are used all over the Internet in various howtos. Thank you russell for spotting this problem. I propose to revert this change and make sysupgrade use "firmware" instead. This makes brcm47xx compatible with widely used ar71xx and after all "firmware" sounds like a much better name for... the firmware. This change doesn't affect "sysupgrade" usage, because it never takes a partition name as a parameter. This change only affects users using mtd tool directly. Hopefully there are not many howtos using "mtd" command. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 38973
* brcm47xx: fix netconfig for inverted vlan?ports in nvramHauke Mehrtens2013-11-111-2/+4
| | | | | | This was observed on the Belkin Share F7D7302. SVN-Revision: 38769
* brcm47xx: add support for ipv6 in default network configHauke Mehrtens2013-10-021-58/+40
| | | | | | | | | Modify /etc/init.d/netconfig to use UCI defaults for building the default network config, which includes appropriate defaults for IPV6. Signed-off-by: Nathan Hintz <nlhintz@hotmail.com> SVN-Revision: 38294
* brcm47xx: run mtd fixtrx linux every timeHauke Mehrtens2013-07-311-8/+1
| | | | | | | | With this patch it is possible to boot a device with kernel 3.10 a second time. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 37625
* brcm47xx: use b53 phy driver for the switch in kernel 3.10Hauke Mehrtens2013-07-141-4/+4
| | | | | | | | | | This makes it possible to use swconfig to controll the switch. This was tested with devices using b43 and bgmac. This was not tested on devices using tg3. This does not support the adm switch used in some very old devices. SVN-Revision: 37304
* brcm47xx: use old partition names again for kernel 3.8Hauke Mehrtens2013-04-061-1/+1
| | | | | | | | This fixes sysupgrade. The partition names are used all over the Internet in various howtos. Thank you russell for spotting this problem. SVN-Revision: 36235
* brcm47xx: netconfig: add bacis support for swconfigHauke Mehrtens2013-03-091-25/+27
| | | | | | Parse the cpu port from swconfig and explicitly mark the cpu port as tagged. SVN-Revision: 35911
* brcm47xx: do not use vlan0 any more.Hauke Mehrtens2013-02-201-40/+40
| | | | | | | | The Broadcom switch driver says that vlan0 should not be used with any switch other than bcm5325. This makes OpenWrt always use vlan1 and vlan2 instead. SVN-Revision: 35704
* brcm47xx: add initial support for kernel 3.8Hauke Mehrtens2013-02-161-0/+14
| | | | | | | | | | | | This contains the following new bigger changes: * new partition parser which still could lake some features or have bugs * new nand flash driver * using physmap-flash flash driver for parallel flash * some changes to the serial flash driver With these changes OpenWrt starts using more of the mainline flash drivers. SVN-Revision: 35632
* brcm47xx: fix network config on simpleshareHauke Mehrtens2013-02-161-0/+6
| | | | | | | | | | The included patch will generate a correct network configuration on the simpletech simpleshare. Thank you for the patch Will Holmes (RealOpty) This closes #12361. SVN-Revision: 35623
* brcm47xx: try to automatically detect if the wan port is at port 4 and not ↵Hauke Mehrtens2013-02-161-1/+12
| | | | | | | | at port 0. This should fix #13000. SVN-Revision: 35617
* brcm47xx: if the cpuport of the switch is port 8 assume vlan0ports: "1 2 3 4 ↵Hauke Mehrtens2013-02-141-16/+8
| | | | | | 8" and vlan0ports: "0 8" SVN-Revision: 35597
* brcm47xx: configure vlan correctly on some recent devices.Hauke Mehrtens2013-02-131-1/+4
| | | | SVN-Revision: 35587
* brcm47xx: Fix switch config on 4716/53115 devicesHauke Mehrtens2013-02-041-1/+1
| | | | | | Signed-off-by: Jonathan McCrohan <jmccrohan@gmail.com> SVN-Revision: 35490
* brcm47xx: Additional BCM4716 supportHauke Mehrtens2012-12-131-0/+6
| | | | | | | | Additional BCM4716 support. Still needs working ethernet driver. Signed-off-by: Nathan Hintz <nlhintz@hotmail.com> SVN-Revision: 34672
* add vlan definitions for Siemens SE505v2Florian Fainelli2011-09-301-3/+2
| | | | | | | | | | | | | | | | | | Hi, this patch adds the correct vlan definitions for the Siemens SE505v2. It applies to trunk as well as backfire (please apply here too). On backfire this also patches brcm-2,4, because brcm47xx base-files is just symlinked to brcm-2.4. It also fixes two whitespace issues. Tested with brcm47xx on both trunk and backfire branch and works as expected. Signed-off-by: Manuel Munz <freifunk@somakoma.de> SVN-Revision: 28336
* fix the default network configuration for the ASUS WL-330gE (#8751)Jo-Philipp Wich2011-08-171-2/+2
| | | | SVN-Revision: 28024
* add back the base-files/image code from brcm-2.4 to brcm47xxFelix Fietkau2010-06-263-0/+309
SVN-Revision: 21945
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-01 08:42:45 +0000