aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm53xx/image
Commit message (Collapse)AuthorAgeFilesLines
* bcm53xx: enable Linksys EA6300 & EA9200 buildsRafał Miłecki2021-12-131-3/+0
| | | | | | | | | | | Both should be supported since: 1. Adding NVMEM driver for NVRAM 2. Using NVRAM info for determining active firmware partition Linksys EA9500 uses very similar design and works fine. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 287257d676b1120f388120f1dc259e4eefd3b163)
* bcm53xx: enhance support for Linksys EA9500Vivek Unune2021-04-081-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Add leds and configs 2. Add network configs 3. Add script to clear partial boot flag 4. Hack to use port 5 as cpu port as port 8 connected to eth2 wont pass any frames 5. Enable EA9500 image generation Hardware Info: - Processor - Broadcom BCM4709C0KFEBG dual-core @ 1.4 GHz - Switch - BCM53012 in BCM4709C0KFEBG & external BCM53125 - DDR3 RAM - 256 MB - Flash - 128 MB (Toshiba TC58BVG0S3HTA00) - 2.4GHz - BCM4366 4×4 2.4/5G single chip 802.11ac SoC - Power Amp - Skyworks SE2623L 2.4 GHz power amp (x4) - 5GHz x 2 - BCM4366 4×4 2.4/5G single chip 802.11ac SoC - Power Amp - PLX Technology PEX8603 3-lane, 3-port PCIe switch - Ports - 8 Ports, 1 WAN Ports - Antennas - 8 Antennas - Serial Port - @j6 [GND,TX,RX] (VCC NC) 115200 8n1 Flashing Instructions: 1. Connect a USB-TTL table to J6 on the router as well as a ethernet cable to a lan port and your PC. 2. Power-on the router. 3. Use putty or a serial port program to view the terminal. Hit Ctrl+C and interrupt the CFE terminal terminal. 4. Setup a TFTP server on your local machine at setup you local IP to 192.168.1.2 5. Start the TFTP Server 6. Run following commands at the CFE terminal flash -noheader 192.168.1.2:/openwrt.trx nflash0.trx flash -noheader 192.168.1.2:/openwrt.trx nflash0.trx2 nvram set bootpartition=0 && nvram set partialboots=0 && nvram commit 7. Reboot router to be presented by OpenWrt Note: Only installation method via serial cable is supported at the moment. The trx firmware has to be flashed to both the partitions using following commands from CFE prompt. This will cover US and Non-US variants. Signed-off-by: Vivek Unune <npcomplete13@gmail.com> Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 209c5918b511d9e406a094ba246a985b640e519f)
* target: use SPDX license identifiers on MakefilesAdrian Schmutzler2021-02-101-4/+2
| | | | | | Use SPDX license tags to allow machines to check licenses. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm53xx: use default SUPPORTED_DEVICES for Meraki MR32Adrian Schmutzler2021-01-231-3/+1
| | | | | | | | Since the new global SUPPORTED_DEVICES are now available in bcm53xx as well, we do not need to specify an explicit value for the MR32 anymore. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm53xx: use correct case for TP-Link in DEVICE_VENDORMoritz Warning2020-12-191-2/+2
| | | | | | | | Adjust spelling of vendor names to what is used in other places. Signed-off-by: Moritz Warning <moritzwarning@web.de> [improve commit title/message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm53xx: MR32: fix DEVICE_VENODR typoChristian Lamparter2020-12-131-1/+1
| | | | | | DEVICE_VENDOR was misspelled as DEVICE_VENODR. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bcm53xx: add Cisco Meraki MR32Christian Lamparter2020-09-251-0/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for Cisco Meraki MR32. The unit was donated by Chris Blake. Thank you! WARNING: Only the 1x1:1 abgn Air Marshal WIPS wifi is currently supported by b43: b43-phy2: Found PHY: Analog 9, Type 4 (N), Revision 16 b43-phy2: Found Radio: Manuf 0x17F, ID 0x2057, Revision 9, Version 1 b43-phy2: Loading firmware version 784.2 (2012-08-15 21:35:19) and only as 802.11ABG! while WIFI1 and WIFI2 (both BCM4352) are not: b43-phy0: Broadcom 4352 WLAN found (core revision 42) b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1) Hardware Highlights: SoC: Broadcom BCM53016A1 (1 GHz, 2 cores) RAM: 128 MiB NAND: 128 MiB Spansion S34ML01G2 (~114 MiB useable) ETH: 1GBit Ethernet Port - PoE WIFI1: Broadcom BCM43520 an+ac (2x2:2 - id: 0x4352) WIFI2: Broadcom BCM43520 bgn (2x2:2 - id: 0x4352) WIFI3: Broadcom BCM43428 abgn (1x1:1 - id: 43428) BLE: Broadcom BCM20732 (ttyS1) LEDS: 1 x Programmable RGB Status LED (driven by a PWM) 1 x White LED (GPIO) 1 x Orange LED Fault Indicator (GPIO) 2 x LAN Activity / Speed LEDs (On the RJ45 Port) BUTTON: one Reset button MISC: AT24C64 8KiB EEPROM (i2c - stores Ethernet MAC + Serial#!) ina219 hardware monitor (i2c) Kensington Lock SERIAL: WARNING: The serial port needs a TTL/RS-232 3V3 level converter! The Serial setting is 115200-8-N-1. The board has a populated right angle 1x4 0.1" pinheader. The pinout is: VCC, RX, TX, GND. (Use a multimeter) Flashing needs a serial adaptor (due to the lack of a working dropbear on the original firmware). This flashing procedure for the MR32 was tested with firmware: "r23-149867:150252-aacharya". 0. Create a seperate Ethernet LAN which does not have access to the internet. Ideally use 192.168.1.2 for your PC. Make sure to reserve 192.168.1.1 it will be used later on by the OpenWrt firmware. The original Meraki firmware will likely try to setup the network via DHCP Discovery, so make sure your PC is running a DHCP-Server (i.e.: dnsmasq) '# dnsmasq -i eth# -F 192.168.1.5,192.168.1.50 Furthermore, the PC needs a supported ssh/http/ftp server in order to retrieve the initramfs + dtb file 1. Disassemble the MR32 device by removing all screws (4 screws are located under the 4 rubber feets!) and prying open the plastic covers without breaking the plastic retention clips. Once inside, remove all the screws on the outer metal shielding to get to the PCB. It's not necessary to remove the antennas! 2. Connect the serial cable to the serial header. 3. Partially reassemble the outer metal shielding to ensure that the SoC has a proper heat sink. 4. Connect the Ethernet patch cable to the device and the power cable. 5. Wait for the device to boot and enter the root shell. (rooting is not discussed in detail here please refer to Chris Blake - "pwning the meraki mr18" blog post: <https://servernetworktech.com/2016/02/pwning-the-meraki-mr18/> (The same method works with the MR32's r23-149867:150252-aacharya) Wait for the MR32 to enter the "<Meraki>" prompt and enter: <Meraki> odm serial_num read (Verify that it matches what's on the S/N Sticker on the back!) <Meraki> odm serial_num write Q2XX-XXXX-XXXV <Meraki> odm serial_num read (Verify that the S/N has changed - and the LED start to flash) now to flash the firmware: <Meraki> odm firmware part.safe "http://192.168.1.2/mr32-initramfs.bin" Once OpenWrt booted use sysupgrade to permanently install OpenWrt. To do this: Download the latest sysupgrade.bin file for the MR32 to the device and use sysupgrade *sysupgrade.bin to install it. WARNING: DO NOT DELETE the "storage" ubi volume! To flash later MR32 Firmwares like r25-201804051805-G885d6d78-dhow-rel requires in-circut-i2c tools to access the I2C EEPROM AT24C64 next to the SoC. The idea is pretty much the same as from Step 5 from above: Change the serial number to Q2XXXXXXXXXV (should be around 0x7c), then attach a serial cable, ethernet (but make sure the device can't reach the internet!) hit "s" (the small s!) during boot to enter the root-shell and add the following commands to the /storage/config there: serial_allow_odm true serial_access_enabled true serial_access_check false valid_config true and then hit exit to let it finish booting. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* treewide: use wpad-basic-wolfssl as defaultPetr Štetiar2020-08-201-1/+1
| | | | | | | | | | | | | | | In order to support SAE/WPA3-Personal in default images. Replace almost all occurencies of wpad-basic and wpad-mini with wpad-basic-wolfssl for consistency. Keep out ar71xx from the list as it won't be in the next release and would only make backports harder. Build-tested (build-bot settings): ath79: generic, ramips: mt7620/mt76x8/rt305x, lantiq: xrx200/xway, sunxi: a53 Signed-off-by: Petr Štetiar <ynezz@true.cz> [rebase, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm53xx: use vendor_model scheme for device/image namesAdrian Schmutzler2020-08-121-57/+57
| | | | | | | | | | | Most targets have been updated to consistently use the vendor_model scheme for device definitions and thus, image names. Apply this to bcm53xx as well. This does _not_ apply any other specific naming changes. Cc: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: mark devices as BROKEN instead of commenting outPetr Štetiar2020-07-301-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the newly introduced BROKEN flag to a bunch of devices that previously just had TARGET_DEVICES commented out. By this, we can select them in make menuconfig when BROKEN developer config option is selected, instead of having to edit the code. In contrast to DEFAULT := n, this is meant to cover devices that don't boot or don't compile at all. ath25: np25g, wpe53g both disabled during kernel bump 3.18->4.4 without reason given f89a20a89aeb ("ath25: update kernel from 3.18 to 4.4") bcm53xx: linksys-ea6300-v1, linksys-ea9200, linksys-ea9500 broken due to insufficient/broken TRX support 55ff15cfd509 ("bcm53xx: disable building Linksys EA6300 V1 image") cd0f9900a4cd ("bcm53xx: parepare for building more Linksys images") bcm63xx: tplink-archer-c5-v2, tplink-archer-c9-v1 disabled when kernel 5.4 support was added, probably broken 50c6938b95a0 ("bcm53xx: add v5.4 support") Signed-off-by: Petr Štetiar <ynezz@true.cz> [limit to subset of devices, use BROKEN, adjust commit message/title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: use DEFAULT := n to disable non-broken devicesPetr Štetiar2020-07-301-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This uses DEFAULT := n on a bunch of devices that previously were "disabled" by commenting out TARGET_DEVICES. This will allow to build them without having to modify the code, but they will not be selected for default build or buildbots. The change is applied to all devices that are not "broken", but suffer from image site limitations or similar, or have been added in the past but never confirmed to run on the device properly: at91: at91-q5xr5: kernel image too big 31aeae077482 ("at91: do not build image for at91-q5xr5") bcm47xx: asus-rt-ac66u: disabled since it was added in 2015 69aefc771fd8 ("brcm47xx: build images for Asus devices") bcm47xx: netgear-wndr3400-vcna, netgear-wnr3500u, netgear-wnr3500-v2-vc added disabled in 2012, but never confirmed to work on devices 5dec9dd3b200 ("brcm47xx: add code to generate images for some netgear devices") bcm53xx: netgear-r8500 added disabled: "start working on Netgear R8500" 3b76c7cf0bdd ("bcm53xx: start working on Netgear R8500") Signed-off-by: Petr Štetiar <ynezz@true.cz> [limit to subset of devices, adjust commit message/title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm53xx: add support for Luxul FullMAC WiFi devicesDan Haab2020-04-071-0/+18
| | | | | | | | | | This prepares support for models XAP-1610 and XWR-3150. Flashing requires using Luxul firmware version: 1) 8.1.0 or newer for XAP-1610 2) 6.4.0 or newer for XWR-3150 and uploading firmware using "Firmware Update" web UI page. Signed-off-by: Dan Haab <dan.haab@legrand.com>
* bcm53xx: fix ASUS firmwares to use vendor formatRafał Miłecki2020-03-021-6/+13
| | | | | | | | Image building process was missing "asus-trx" step which resulted in raw TRX files (without ASUS footer with device id). Fixes: 0b9de8daa70e ("bcm53xx: add profiles for all other (SoftMAC) devices") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add v5.4 supportJohn Crispin2020-02-281-2/+2
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* bcm53xx: build images for Luxul ABR-4500 and XBR-4500 routersDan Haab2020-02-071-0/+30
| | | | | | | | Luxul ABR-4500 and XBR-4500 devices are wired routers with 5 Ethernet ports and 1 USB 3.0 port. Flashing requires using Luxul firmware 6.4.0 or newer and uploading firmware using "Firmware Update" web UI page. Signed-off-by: Dan Haab <dan.haab@legrand.com>
* bcm53xx: split up DEVICE_TITLEMoritz Warning2019-08-021-24/+46
| | | | | | DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Signed-off-by: Moritz Warning <moritzwarning@web.de>
* bcm53xx: add support for Phicomm K3Hao Dong2019-01-201-0/+7
| | | | | | | | | | | | | | | | | | | | | | | Hardware specifications: - CPU: Broadcom BCM4709C0 @1.4GHz (Dual-Core ARM) - RAM: 512 MB (DDR3) - Flash: 128 MB (NAND) - LAN ports: 3, LAN speed: 10/100/1000 - WAN ports: 1, WAN speed: 10/100/1000 - 2.4G: BCM4366 4x4 MIMO 1000Mbps -- Skyworks SE2623L 2.4GHz Power Amplifier (x4) - 5G: BCM4366 4x4 MIMO 2167Mbps -- RFMD RFPA5542 5GHz Power Amplifier Module (x4) - USB: 1x USB 3.0 port - 1x LED, 1x reset button, 1x power switch - 1x system status touch screen Flash: - Enter CFE - Upload the trx file - Reboot Signed-off-by: Hao Dong <halbertdong@gmail.com>
* bcm53xx: include WiFi firmware for devices with 4366C0Rafał Miłecki2018-12-171-1/+1
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: use wpad-basic for not small flash targetsMathias Kresin2018-10-161-1/+1
| | | | | | | | | | | | Add out of the box support for 802.11r and 802.11w to all targets not suffering from small flash. Signed-off-by: Mathias Kresin <dev@kresin.me> Mathias did all the heavy lifting on this, but I'm the one who should get shouted at for committing. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* bcm53xx: added basic dts for linksys ea6500v2Rene Kjellerup2018-10-071-1/+6
| | | | | | | | only thing not working is the b43 5GHz wifi band as upstream kernel doesn't supporthe 0x4360 chip so far Signed-off-by: Rene Kjellerup <rk.katana.steel@gmail.com>
* bcm53xx: drop not ready support for Luxul devicesRafał Miłecki2018-06-181-30/+0
| | | | | | | | Support for these devices isn't ready yet and it was only accidentally pushed in the commit 0da9303e5b44 ("mac80211: backport "brcmfmac: cleanup and some rework" from 4.17"). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* mac80211: backport "brcmfmac: cleanup and some rework" from 4.17Rafał Miłecki2018-06-171-0/+30
| | | | | | | | | | | It was described by Arend as: > This series is intended for 4.17 and includes following: > > * rework bus layer attach code. > * remove duplicate variable declaration. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: use otrx for creating TRX imagesRafał Miłecki2017-11-171-6/+2
| | | | | | | | The advantage is that we don't have to specify max TRX size anymore and otrx doesn't allocate a buffer of that size. It saves us allocating 32 MiB for every image we generate. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: Fix SmartRG SR400AC initramfs imageFlorian Fainelli2017-10-231-0/+2
| | | | | | | The SmartRG SR400AC CFE does not accept a TRX image, just a normal binary image. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* bcm53xx: include wpad-mini only on devices with (supported) wirelessRafał Miłecki2017-06-081-12/+14
| | | | | | | Don't include wpad-mini when it's useless just like we don't include useless wireless drivers. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add support for TP-LINK Archer C5 V2Rafał Miłecki2017-05-211-1/+1
| | | | | | | | This model also contains few partitions non-discoverable partitions we need to "protect". Othen than that it uses non-deprecated serial entry in DTS that doesn't work with LEDE so we need to workaround it as well. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: put kernel into TRX when building initramfs imagesRafał Miłecki2017-03-271-0/+25
| | | | | | | | | | | Many (most?) devices can't boot raw kernel using tftp and probably none allows flashing it. It's way more usable to have TRX with kernel containing initrams as such an image can be actually flashed. An exception are Buffalo devices which have recovery mode with support for booting kernels over TFTP. For them keep building default images. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: parepare for building more Linksys imagesRafał Miłecki2017-03-121-1/+16
| | | | | | We still can't enable them by default without proper TRX support. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: prepare for building Archer C5 V2 imageRafał Miłecki2017-03-111-0/+9
| | | | | | Don't enable it yet as kernel needs to be updated first. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: image: use one style of adding TARGET_DEVICES entriesRafał Miłecki2017-02-061-4/+4
| | | | | | | It just makes code consistent. This trivial change may be a 17.01 candidate to provide simpler backporting experience. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: build factory images for WZR-900DHP seriesFUKAUMI Naoki2017-01-311-0/+26
| | | | | | | | | | only factory images for DHP-EU and DHP2-JP (fw ver. 2.x) are built. this will not work for DHP-JP/AP/TW (fw ver. 1.x) because they use different buffalo_csum() formula. Signed-off-by: FUKAUMI Naoki <naobsd@gmail.com> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: disable building Linksys EA6300 V1 imageRafał Miłecki2017-01-251-1/+2
| | | | | | | This device has 2 TRX partitions (main one and failsafe one) and Linux may not detect them properly failing to run userspace. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: build image for TP-LINK Archer C9 v1Rafał Miłecki2016-11-191-1/+26
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: include b43 in Tenda AC9 imageRafał Miłecki2016-10-201-1/+1
| | | | | | There is some (poor?) support for BCM43217 in b43. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: include usbport trigger for devices with USBRafał Miłecki2016-10-191-0/+1
| | | | | | | We don't have any code for enabling it automatically yet but it allows adding entries manually to the /etc/config/system. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: use the latest XHCI doorbell patch sent for upstreamRafał Miłecki2016-10-021-1/+1
| | | | | | | The main difference is it supports DT binding. This allows us to use DT for specifying controller and the new standalone USB 3.0 PHY driver. Thanks to that we don't need out of tree patch adding PHY initialization to the controller driver anymore.
* bcm53xx: switch to standalone USB 2.0 PHY driverRafał Miłecki2016-10-011-2/+2
| | | | | | | This drops built-in support for USB 2.0 PHY and starts using separated driver that was upstreamed & backported some time ago. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: specify brcmfmac firmware for every deviceRafał Miłecki2016-09-131-5/+7
| | | | | | | This will allow us to include required firmwares only and save some rootfs space. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* build: drop UBI EOF marker from images by defaultFelix Fietkau2016-09-121-1/+0
| | | | | | | | Only add them where they are actually required. Should help with compatibility issues with stock U-Boot images that access UBI Signed-off-by: Felix Fietkau <nbd@nbd.name>
* image: use k as unit suffix for blocksizeMathias Kresin2016-09-041-1/+1
| | | | | | | Use k as unit suffix for kilobyte to have a the same unit regardless of the used filesystem. Signed-off-by: Mathias Kresin <dev@kresin.me>
* bcm53xx: build Tenda AC9 imageRafał Miłecki2016-08-191-1/+1
| | | | | | | | We finally got kernel booting on this device and LAN ports are working, so it won't "brick" the device. One more big missing thing is WAN port support. It requires fix for BCM53125 to get switch port 5 working. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: prepare for building Tenda AC9 TRX imageRafał Miłecki2016-08-151-0/+8
| | | | | | It'll be enabled when we complete basic support. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add profiles for Buffalo devicesRafał Miłecki2016-08-111-2/+24
| | | | | | | This generates proper images when using CONFIG_TARGET_MULTI_PROFILE and CONFIG_TARGET_PER_DEVICE_ROOTFS. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: include USB modules in images for devices with USB portsRafał Miłecki2016-08-111-9/+16
| | | | | | This allows using USB out of the box. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add profiles for all other (SoftMAC) devicesRafał Miłecki2016-08-111-31/+34
| | | | | | | Thanks to this images for SoftMAC devices don't get brcmfmac anymore and b43 is added for devices with (quite poor) support only. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: convert (disabled) Netgear R8500 image to own profileRafał Miłecki2016-08-111-1/+8
| | | | | | It should be the last device with FullMAC chipset to convert. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add profile with brcmfmac for Netgear R7900Rafał Miłecki2016-08-111-1/+8
| | | | | | | It's one more device with FullMAC that got forgotten in the previous commit. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add profiles for devices with FullMAC chipsetsRafał Miłecki2016-08-101-1/+12
| | | | | | | | This allows building images for selected devices with brcmfmac only (without b43 which is for SoftMAC devices). Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Reviewed-by: Jo-Philipp Wich <jo@mein.io>
* image: add a helper variable for getting kernel/rootfs from within image ↵Felix Fietkau2016-07-311-3/+3
| | | | | | Build/* templates Signed-off-by: Felix Fietkau <nbd@nbd.name>
* image.mk: clean up redundant code related to DEVICE_DTSFelix Fietkau2016-07-151-1/+1
| | | | | | | | It is used by a core build template, so the variable should be initialized and added to DEVICE_VARS in the core. Same for DEVICE_DTS_DIR Signed-off-by: Felix Fietkau <nbd@nbd.name>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 01:38:12 +0000