aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/DWR-512-B.dts
Commit message (Collapse)AuthorAgeFilesLines
* ramips: add dwr-512 jboot firmware configurationGiuseppe Lippolis2018-04-081-10/+4
| | | | | | | | | | | | | | | | | | | | | The previous fw version require the replacement of the stock bootloader with u-boot. This prevent an easy stock restore of the original fw. Now a proper fw util has been developed to manage the stock jboot bootloader. Therefore make sense have a fw image for the stock bootloader. The old fw configuration (u-boot) is not compatible with the new one and will not be supported anymore. So at the end 2 image can be generated: 1) factory image with jboot bootloader openwrt-ramips-rt305x-dwr-512-b-squashfs-factory.bin 2) sysupgrade image with jboot bootloader openwrt-ramips-rt305x-dwr-512-b-squashfs-sysupgrade.bin Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ramips: fix polarity in gpio-export nodeMathias Kresin2017-12-181-1/+1
| | | | | | | | If we need to set the initial output value to GPIOF_OUT_INIT_HIGH (1) to enable something, the pin is ACTIVE_HIGH. The same applies to GPIOF_OUT_INIT_LOW (0) and ACTIVE_LOW. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: update device tree source filesL. D. Pinney2017-08-031-1/+1
| | | | | | | | Use the GPIO dt-bindings macros and add compatible strings in the ramips device tree source files. Signed-off-by: L. D. Pinney <ldpinney@gmail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix wps button gpio for DWR-512Giuseppe Lippolis2017-07-251-1/+1
| | | | | | The WPS button is at GPIO#7. Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ramips: export slic IRQ line in dwr-512Giuseppe Lippolis2017-02-151-0/+4
| | | | | | | | The DWR-512 embeds the hw slic device si3210. This device have the IRQ line attached to the gpio1. This patch export the gpio1 with proper name and parameters to the sysfs. Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ramips: fixed sms led polarity into dwr-512 DTGiuseppe Lippolis2017-02-141-1/+1
| | | | Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ramips: adding registration for si3210Giuseppe Lippolis2016-12-201-0/+13
| | | | | | | | | | | | | | | The si3210 is a SLIC device providing a complete analog telephone interface and therefore frequently used in soho router. The si3210 have a native spi interface to be controlled by the CPU but currently there is no dedicated driver in lede. Adding a registration for this device in spidev allow to control the device in user space. This way of patching is also in line with the rationale of the spidev driver, see: http://marc.info/?t=148145791900001&r=1&w=2 The si3210 has been also added in the DWR-512 DT to properly describe the HW. Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ramips: Add device DLINK DWR-512-BGiuseppe Lippolis2016-11-231-0/+128
The Dlink DWR-512-B modem is a ralink 5350 processor based embedding a 3G mini-pcie router. The oem JBOOT bootloader has to be replaced by a RT5350 SDK U-Boot such as https://github.com/stevenylai/ralink_sdk - U-Boot configured for the RT5350 256MiB SDR. Main reason to change the bootloader is the encrypted header used to store the kernel image. In this way an image can only be generated using the propietary binboy tool (included in the GPL distribution from Dlink). The binboy tool doesn't allow to modify the kernel/rootfs partition scheme. This is considered a big constraint (limited kernel size and inefficient usage of flash space). For interested people I pubblished the details of my investigation about the encrypted firmware header here: http://lists.infradead.org/pipermail/lede-dev/2016-October/003435.html Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>