| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old signature only worked because brnboot ignores the leading "5" in
the signature. We can see the correct signature when flashing a brnImage
via recovery web-interface, in this case brnboot reports:
[CGI-Signature Check] buf:[BRNDA6431], sigInFlash:[BRNDA6431]
Thanks to Mathias Kresin for reporting this.
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
SVN-Revision: 48269
|
|
|
|
|
|
| |
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 48002
|
|
|
|
|
|
|
|
|
| |
The device is similar to the TD-W8970, beside a different Atheros 2.4 GHz
wireless chip and the additional, PCI connected, WAVE300 5 GHz wireless.
Signed-off-by: Mathias Kresin <openwrt@kresin.me>
SVN-Revision: 47130
|
|
|
|
| |
SVN-Revision: 47105
|
|
|
|
|
|
|
|
|
|
| |
Support for lantiq_svip_be has been removed a while ago, so EASY33016
images weren't buildable anymore. Remove the recipes as well as gzip
compressed kernel support, as EASY33016 was the last user of it.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 46760
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of each target defining it the same, move the KDIR_TMP
definition to include/image.mk. In addition Image/Build/SysupgradeNAND
already requires KDIR_TMP to be set, so it makes sense to have it
globally defined.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 46592
|
|
|
|
|
|
|
|
|
|
|
|
| |
Variables dependend on JFFS2_BLOCKSIZE and NANDBLOCK_SIZE are used
for template generation, so need to be present before inclusion of
image.mk in target image Makefiles.
So move all declarations to before any includes.
Fixes: r42878 ("image.mk: clean up and parallelize mkfs calls")
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 46564
|
|
|
|
|
|
|
|
| |
lantiq: Add support for Arcadyan ARV8539PW22 (Speedport W 504V)
Signed-off-by: Jannis Pinter <jannis@pinterjann.is>
SVN-Revision: 46224
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
u-boot support depends on the next "upstream" version ([0]) from
Daniel Schwierzeck.
Since the installation process is quite complicated a "how to" was
added to the wiki: [1]
[0] https://github.com/danielschwierzeck/u-boot-lantiq/tree/openwrt/v2014.01-next
[1] http://wiki.openwrt.org/toh/bt/homehub_v5a
V2: Use the correct PCI interrupt (fixes 2.4GHz wifi)
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
SVN-Revision: 46223
|
|
|
|
| |
SVN-Revision: 45897
|
|
|
|
|
|
|
|
|
| |
This also adds the old hardcoded value to the VGV7519BRN profile to make
sure that images are still generated correctly.
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
SVN-Revision: 45882
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 45851
|
|
|
|
|
|
|
|
| |
the kernel has increased and does not fit into the 1,5MB anymore.
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 44391
|
|
|
|
|
|
|
|
| |
Add profile and userspace for P2812HNUF1/3, switch from UBI_GLUEBI to UBI_BLOCK
Signed-off-by: Sylwester Petela <sscapi@gmail.com>
SVN-Revision: 43987
|
|
|
|
|
|
|
|
| |
BT Home Hub 3A - profile
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 43878
|
|
|
|
|
|
| |
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
SVN-Revision: 42183
|
|
|
|
|
|
|
|
|
|
| |
New make target in lantiq to use UbinizeImage and SysupgradeNand.
Only enabled for BTHOMEHUBV2B for the moment but should be useable
for other lantiq nand boards.
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 41474
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As far as I am aware, amongst the lantiq boards, jffs2_nand was
only used on the BTHOMEHUBV2B. Ubi-related modifications to the
device tree for that board mean that the resulting jffs2 images
no longer work, and are no longer required anyway. So I suggest
removing the related configuration, which this patch does.
If anyone else is using jffs2_nand on a lantiq target please speak
up!
Incidentally, for a jffs2 rootfs partition concatenated to the
kernel image to be recognised and mounted correctly on nand
this patch or something equivalent is required:
http://patchwork.openwrt.org/patch/5110/
It is marked as accepted in patchwork but doesn't seem to have
been committed. As far as I am concerned it too is deprecated.
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 41312
|
|
|
|
|
|
|
|
|
| |
Setting this flag allows rootfs_data to expand on first boot
to fill remaining free space on nand.
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 41310
|
|
|
|
|
|
|
|
|
| |
At the moment, an rootfs.ubi is copied over to bin/lantiq
but rootfs-overlay.ubi is not. This adds it.
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 41270
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
support
This patch adds factory image building for the DGN3500, all variants,
and fixes sysupgrade images to make them play nice with the sercomm
secondary boot loader.
The factory images can be used directly in the update dialog in the
interface of the stock firmware and via the special Sercomm bootmode
and a special windows flashing utility (allegedly present in the CD
that came with the device -- but it's also compatible with the NSLU2
Upgrade_207_XP utility.) The special bootmode can be activated by
turning the device on while holding the reset button pressed, then
releasing it when the power led starts blinking red and green. Please
notice that if using the 207 utility, it will always report that the
flashing failed even though it completed successfully. Just power
cycle the router manually after the utility reports the failure and
OpenWRT will boot. This same utility (despite reporting failure in
this case too) can revert a DGN3500 (any variant) to the appropriate
stock Netgear firmware.
This patch is a heavily modified version of a package I found on the
OpenWRT forum with a couple fixes and features added -- mainly the
generation of all the different image variants to support all known
models directly, atm known variants are AnnexA-WW, AnnexA-NA and
AnnexB-DE/GR.
I tested the patch successfully on my device.
Signed-off-by: Marco Antonio Mauro <marcus90@gmail.com>
SVN-Revision: 41236
|
|
|
|
|
|
|
|
| |
This patch moves ARV7519RW definitions to VR9 section from the AR9 section and removes a whitespace that breaks jffs2 image generation.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
SVN-Revision: 40495
|
|
|
|
|
|
|
|
|
| |
this should really be auto detected by the kernel, lets used this workaround until the real
solution is ready
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 40418
|
|
|
|
|
|
|
|
| |
Board support patch for BT Home Hub 2B
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 40370
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 40364
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These patches add support for the Astoria ARV7519RW aka Livebox 2.1
The PCI and PCIe interfaces have been disabled. Also, because there are
two revisions of this board with different GPHY firmwares, two targets
were defined.
V2: rewrote partitions to work with an u-boot specifically made for
these boards.
Signed off by: Esteban Benito <estebanjbs@gmail.com>
Signed off by: Carles Gadea <carlesgrg@gmail.com>
Tested by: José Vázquez Fernández <ppvazquezfer@gmail.com>
SVN-Revision: 40329
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds almost full support for this board.
- WiFi is still not working
- USB will not power up. According to some reports, it may be a passive port
Signed-off-by: Antonios Vamporakis <ant@area128.com>
SVN-Revision: 40319
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds almost full support for this board. WiFi is still not working.
The FXS ports are not functional due to missing support for the TAPI driver on
VR9 SoC.
Signed-off-by: Antonios Vamporakis <ant@area128.com>
Tested-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 40317
|
|
|
|
|
|
| |
Signed-off-by: Antonios Vamporakis <ant@area128.com>
SVN-Revision: 40316
|
|
|
|
|
|
|
|
| |
This board is pretty similar to ARV752DPW22.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
SVN-Revision: 39303
|
|
|
|
|
|
|
|
| |
https://dev.openwrt.org/ticket/14417
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 38667
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 38326
|
|
|
|
|
|
|
| |
Signed-off-by: Maikel Bloemendal <mbloemendal@gmail.com>
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 38266
|
|
|
|
|
|
| |
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 38051
|
|
|
|
|
|
| |
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 38050
|
|
|
|
| |
SVN-Revision: 38049
|
|
|
|
|
|
| |
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 38048
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 38029
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 37727
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 37722
|
|
|
|
|
|
|
|
|
|
| |
*) can not connect to switch chip
*) only one usb port is working
*) wifi is not working
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 37712
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 37543
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 37540
|
|
|
|
|
|
| |
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 37178
|
|
|
|
|
|
| |
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 37143
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 36443
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 36440
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 36439
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 36438
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this adds basic support. the bootloader on these units is locked down.
until we have a replacement we can do basic testing with these env variables in uboot.
set update_openwrt erase 0xb0020000 0xb073ffff \;tftp 0x81000000 openwrt-lantiq-xway-VG3503J-squashfs.image\;cp.b 0x81000000 0xb0020000 \$(filesize)
set bootcmd cp.b 0xb0020000 0x80002000 0x400000\; go 0x80002000
unfortunatley the bootloader ignores the bootcmd, so autobooting is not possible yet. you need to call "run bootcmd" by hand after each power cycle.
please note that the vdsl firmware is non redistributable. you can find it in the GPL drop that BT provides.
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 36315
|