There is already a patch for this in openwrt, so it should work (in theory).
Do you use trunk or backfire or something older?
2010/5/25 Matthias Buecher / Germany <m...@maddes.net>:
> Today I checked out how to access the U-Boot variables of my WRT350N v2
> (Orion) from Linux.
>
> Installed uboot-envtools and created a fitting /etc/fw_env.config:
> # WRT350N v2
> # MTD device name Device offset Env. size Flash sector size
> /dev/mtd5 0x0003c000 0x00002000 0x00001000
>
> I can read all U-Boot env vars, but not change any.
> This seems to be a problem of the huge erase site 0x00010000 of mtd.
> Can I specify a separate erase size for the U-Boot partition?
>
>
> static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
> {
> ...
> }, {
> .name = "u-boot",
> .offset = 0x007c0000,
> .size = 0x00040000,
> }, {
> ...
> },
> };
>
> linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c
>
> OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch
>
> Maddes
>
> --
> http://www.maddes.net/
> Home: Earth / Germany / Ruhr-Area
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
