fix inclusion of functions.sh in dsl_fs init script
without this, the following error is seen during build:
./etc/init.d/dsl_fs: line 4: /lib/functions.sh: No such file or directory
Signed-off-by: Thomas Langer <thomas.langer@lantiq.com>
SVN-Revision: 42575
The bb-rc3 image for the BTHOMEHUBV2B is too big for its
mtd partition. This patch corrects the partition sizes in
the device tree. This patch should really go in before
bb-final, otherwise the BTHOMEHUBV2B images won't be useable.
I do apologise for not spotting this straight away.
Many thanks,
Ben
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 42316
- use full board name
- rename uboot-env partition
- add dsl_fw partition
- remove unneeded pinmux groups
- move gigabit ethernet to LAN
- load mac address from mtd
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
SVN-Revision: 42180
Run lantiq_board_detect from lantiq_board_name and lantiq_board_model.
This was the one thing missing from r41474 for sysupgrade board
detection to work properly.
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 41567
Disables gluebi and enables ubiblock on lantiq xway. Squashfs
images on nand use ubifs instead of jffs2 for the overlay.
I'll leave the equivalent patch for xrx200 to someone who has a
board to test.
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
SVN-Revision: 41565
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
Enable LANTIQ_PHY and LANTIQ_XRX200 only in XRX200 subtarget.
These drivers are not needed for ASE, Danube and AR9.
As side effect PHY11G and PHY22F firmwares are not included in the
kernel image, which saves 64 KB.
Signed off by: José Vázquez Fernández <ppvazquezfer@gmail.com>
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 41449
205-fix-headers_install.patch is obseleted by upstream commit 3246a0352e3d58380b9386570f1db1faf7edf8a8
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 41351
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
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 patches the BTHOMEHUB2B device tree to make use of the
new code for automatic detection of the ubi partition and the
rootfs type within it. Gets rid of the ugly alternative bootargs
lines.
Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
Acked-by: Daniel Golle <daniel@makrotopia.org>
SVN-Revision: 41214
ath5k fix in wifi and ethernet eeprom handling patch.
Without the line that adds the patch of_ath5k_eeprom_probe cause a
kernel panic, at least with the ARV4518PW.
Tested only in the modem-router mentioned above.
This patch is based in Bruno's hack present in patch #5454.
Signed off by: Bruno Rodríguez <bruno.rodriguez.1980@gmail.com>
Signed off by: José Vázquez Fernández <ppvazquezfer@gmail.com>
SVN-Revision: 40999
ARGC is a 'C-ism', but not known/valid in shell-syntax - insert the correct
var $# (=number of args) here. under normal conditions this had no impact,
but we should at least correct it. the error was observable like this:
root@box:~ [ -e "/etc/functions.sh" ] && . /etc/functions.sh
root@box:~ [ -e "/lib/functions.sh" ] && . /lib/functions.sh
root@box:~ . /lib/upgrade/platform.sh
root@box:~ . /lib/upgrade/common.sh
root@box:~ platform_check_image /tmp/myfirmware.bin
ash: bad number
root@box:~ echo $?
0
Signed-off-by: Bastian Bittorf <bittorf@bluebottle.com>
SVN-Revision: 40915
The total ethernet frame length should be written to the hardware
register LTQ_ETOP_IGPLEN instead of just the value of the MTU. This
patch fixes network issues on various Danube boards, especially when
VLAN tagging is enabled.
Signed-off-by: Matti Laakso <malaakso at elisanet.fi>
SVN-Revision: 40541
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
* atm module needs to be loaded before linux-atm
* use absolute firmware paths
* extended validation
* add a script for mounting an optional firmware partition
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 40460
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
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
ARV7510PW22, ARV752DPW and ARV752DPW22 have the RT2860 eeprom stored in
flash as big-endian, but the driver needs it in little-endian format. We
have to swab it before handing it over. This requires my earlier patch
for busybox.
Funnily enough, ARV752DPW works also with the incorrect eeprom, but
undoubtedly unoptimally. I have a hunch that also the final remaining
Lantiq board would require this swabbing, but I'm not sure, so I just
swab it in the three boards that I know about.
v2:
* Swab also on ARV7510PW22 based on feedback from Alvaro Rojas
* Fix the offset with bs=2
Signed-off-by: Matti Laakso <malaakso at elisanet.fi>
SVN-Revision: 40328
The existing code only tries to split a parition with name "rootfs"
while actually looking for kernel+rootfs, where usually "firmware" is
used as a partition name. This doesn't make sense, as even if there
was a partition 'rootfs' given by mtdparts or via device-tree, this
code would lead to another partition called 'rootfs' being created
which would not be properly distinguished in the current user-space
code.
While potentially we could use CONFIG_MTD_SPLIT_FIRMWARE_NAME to make
that configurable, the lack of users of brnboot and the fact that we
can freely decide the partition name made me simply change the
hard-coded string constant from "rootfs" to "firmware".
(I'm going to add support for ARV7506PW which run brnboot and needs
this change)
SVN-Revision: 40324
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
Both the GPL driver from ZyXEL and the xrx200 driver have this error. The flags
are reversed. Full duplex is marked as half and the other way around. With this
fix the switch will push full GBit speeds.
Signed-off-by: Antonios Vamporakis <ant@area128.com>
SVN-Revision: 40312
Some ARV4510PW units seem to have unstable PCI due to missing pull-up
resistors. This patch makes sure that the GPIO lines are driven properly.
Signed-off-by: Matti Laakso <malaakso@elisanet.fi>
SVN-Revision: 39587
Arcadyan ARV4510PW has already a build profile in OpenWrt, but it is
severely lacking. This patch brings it up-to-date.
Signed-off-by: Matti Laakso <malaakso@elisanet.fi>
SVN-Revision: 39230
