Sorry about the useless subject, one unconsecrated moment and it was too
late :-)
--
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Hi all,
While trying to integrate a new platform, I tried using the external Git
clone option (CONFIG_KERNEL_GIT_CLONE_URI and friends). This worked
fine, however when the build system came to build the WLAN drivers
(mac80211) package, the built aborted with this error:
default.install
make[3]: L
> Yes, you're right. I want to make sure we have a unique configuration
> for this machine without changing some existing code.
> I'm a bit confused because the WNDR4300 is still marked as "broken".
> So I decided to make a unique one. Also I can't check the image on the
> WNDR4300 because lack o
Signed-off-by: Stefan Agner
---
package/network/utils/iwinfo/src/hardware.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/network/utils/iwinfo/src/hardware.txt
b/package/network/utils/iwinfo/src/hardware.txt
index 66cbe2a..153ffeb 100644
--- a/package/network/utils/iwinfo/src
Detect SoC wireless mac such as AR9340 using the devices modalias
string. Beside PCI IDs the hardware.txt can now contain modalias
strings as device identification.
Signed-off-by: Stefan Agner
---
package/network/utils/iwinfo/src/hardware.txt | 1 +
package/network/utils/iwinfo/src
tinct modalias (see
arch/mips/ath79/dev-wmac.c).
Changes since v1:
- Don't fail if no entry was found
- Renamed modstring to modalias
- Create temporary iface for modalias method as well
Stefan Agner (2):
iwinfo: add Atheros AR9580 to hardware.txt
iwinfo: add device detection using modalias
Detect SoC wireless mac such as AR9340 using the devices modalias
string. Beside PCI IDs the hardware.txt can now contain modalias
strings as device identification.
Signed-off-by: Stefan Agner
---
package/network/utils/iwinfo/src/hardware.txt | 1 +
package/network/utils/iwinfo/src
tinct modalias (see
arch/mips/ath79/dev-wmac.c).
--
Stefan
Stefan Agner (2):
iwinfo: add Atheros AR9580 to hardware.txt
iwinfo: add device detection using modalias
package/network/utils/iwinfo/src/hardware.txt | 2 ++
package/network/utils/iwinfo/src/include/iwinfo.h | 1 +
.../utils/iwinf
Signed-off-by: Stefan Agner
---
package/network/utils/iwinfo/src/hardware.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/network/utils/iwinfo/src/hardware.txt
b/package/network/utils/iwinfo/src/hardware.txt
index 66cbe2a..153ffeb 100644
--- a/package/network/utils/iwinfo/src
Get the factory assigned mac addresses stored in the caldata partition
and asign them to lan, wan and radio1.
Signed-off-by: Stefan Agner
---
package/base-files/files/lib/functions/uci-defaults.sh | 9
+
target/linux/ar71xx/base-files/etc/uci-defaults/02_network | 6 ++
2 files
Nevermind, the second time it worked:
[2.71] UBI: attaching mtd8 to ubi0
[2.74] UBI: EOF marker found, PEBs from 17 will be erased
[2.74] UBI: scanning is finished
[2.77] gluebi (pid 1): gluebi_resized: got update notification
for unknown UBI device 0 volume 1
[
> Weird. For me it was working only at the first boot after flashing the image,
> but any modifications in the fs has been lost after subsequent reboots.
Hm, might be I did not looked at that correctly. Altough, I installed
some packages and I think they were still there after reboot...
Just updat
Hi Gabor
Am 2013-11-06 10:14, schrieb Gabor Juhos:
> I have applied both patches, although I did several modifications in those.
Cool, thanks! Just compiled an image and flashed it, works fine on my
device!
>> By creating a file system manually I tested using UBIFS instead of JFFS2
>> as the ove
).
Signed-off-by: Stefan Agner
---
target/linux/ar71xx/image/Makefile | 92
++---
target/linux/ar71xx/image/ubinize.cfg | 15 ++
target/linux/ar71xx/nand/config-default | 4 +-
3 files changed, 103 insertions(+), 8 deletions(-)
diff --git a/target/linux/ar71xx
Add new subtarget nand with UBI/UBIFS including GLUEBI and squashfs.
This target will be used for NAND based router which make use of
UBI (and maybe UBIFS later on) in order to provide proper NAND
support.
Signed-off-by: Stefan Agner
---
target/linux/ar71xx/Makefile | 2
also noticed that the WAN port on this device does not work
yet. I looked into the code, the platform code only registers one
ethernet device right now. Do you know whats missing there to make WAN
working?
--
Stefan
Stefan Agner (2):
ar71xx: Add new subtarget nand for WNDR4300
ar71xx: Generate
UBIFS needs the whole partition to be empty upon first mounting.
Since the bootloader only flashes the used amount of the UBI
image, this patch padds the image with 0xff.
Signed-off-by: Stefan Agner
---
target/linux/ar71xx/image/Makefile | 17 +++--
1 file changed, 11 insertions
bytes of the rootfs is an UBI magic (ASCII UBI#).
Signed-off-by: Stefan Agner
---
target/linux/ar71xx/image/Makefile | 64
+++--
target/linux/ar71xx/nand/config-default | 2 +-
2 files changed, 63 insertions(+), 3 deletions(-)
diff --git a/target/linux/ar71xx/image
Altered the subtarget nand, use UBI/UBIFS instead of YAFFS2.
Added the first board WNDR4000 to the subtarget to generate
an initramfs image with NAND/UBI/UBIFS support.
Signed-off-by: Stefan Agner
---
target/linux/ar71xx/nand/config-default | 53
-
target/linux
In order to generate UBI root filesytems the ubinize.cfg needs
to be in place. The Makefile provides working default parameters
for WNDR4300 used by the UBI utilities.
Signed-off-by: Stefan Agner
---
target/linux/ar71xx/image/Makefile| 3 +++
target/linux/ar71xx/image/ubinize.cfg | 14
This target will be used for Mikrotik devices using YAFFS2 flash.
The subtarget nand will support NAND devices on UBI/UBIFS.
Signed-off-by: Stefan Agner
---
target/linux/ar71xx/Makefile | 6 +---
target/linux/ar71xx/nand-yaffs2/config-default | 34
ckup" is in between). The rootfs could be UBIFS ro
or squashfs on UBI.
Comments welcome :-)
See also
http://wiki.openwrt.org/toh/netgear/wndr4300
--
Stefan
Stefan Agner (5):
ar71xx: create new subtarget nand-yaffs2
ar71xx: altered subtarget nand for UBI/UBIFS
ar71xx: Added ubinize.cfg
Am 2013-09-27 13:25, schrieb Gabor Juhos:
> 2013.09.25. 11:26 keltezéssel, Gabor Juhos írta:
>> Hm, this is a NULL pointer dereference. It seems that the
>> nand_write_subpage_hwecc function tries to run a callback which is not
>> initialized by the ar934x-nfc driver. I will look into that later.
>
Am 2013-09-24 19:09, schrieb Gabor Juhos:
>> A dd command with conv=noerror leads to a image witch is 16KiB smaller
>> than it should be.
>
> Don't use dd on NAND flashes. Use the nanddump utility from the mtd-utils
> package instead.
Ok I understand that /dev/mtdblock[x] is not the way to handle
Am 2013-09-23 21:08, schrieb Gabor Juhos:
> It should be possible to fix the board via JTAG. At least it seems that the
> PCB
> has an unpopulated JTAG header.
Yes I thought about this too, but since I didn't found an openocd
configuration which should work with this SoC, I didn't even tried it. I
Am 2013-09-17 08:18, schrieb Gabor Juhos:
> 2013.09.16. 1:06 keltezéssel, Stefan Agner írta:
> It is done in software in the ar934x-nfc driver. The NAND controller of the
> AR934x SoCs also supports hardware based ECC calculation but that is not yet
> implemented in the driver. The ha
Hi Gabor,
[resend, forgot mailing list in to list]
> In the early reference driver of the NAND controller, the data from the DMA
> has
> been swapped. On later reference drivers, this swapping has been removed. To
> match with the reference driver, the current ar934x-nfc driver does not swaps
> t
In between I found out that the driver works fine if I erase/write the
NAND first using the driver itself. But when I try to flash something
using the stock U-Boot bootloader, the driver still complains as
outlined in my first message.
Right now I have a running kernel and root filesystem generat
Hi,
This weekend I compiled OpenWRT for my WNDR4300. As stated in the
documentation, only initramfs works currently so I hooked up serial port
and ran the image using U-Boot/TFTP. I created an image with the SoC
NAND driver from Jonus in order to boot an image from NAND flash, but I
get errors whi
Create a pid file by default when starting xinetd (resolves #10342).
Signed-off-by: Stefan Agner
Index: net/xinetd/files/xinetd.init
===
--- net/xinetd/files/xinetd.init (Revision 28720)
+++ net/xinetd/files/xinetd.init
This changes propperly restarts aiccu when the wan interface is
reconnected. This solves the reopened bug #7629.
Signed-off-by: Stefan Agner
Index: ipv6/aiccu/files/aiccu.hotplug
===
--- ipv6/aiccu/files/aiccu.hotplug (Revision
31 matches
Mail list logo
