Weedy wrote... > On 4 January 2017 at 16:29, Christoph Biedl > <[email protected]> wrote: > > Although I understand it's hard to tell: How are the odds the v1.1 > > images will be usable? Or did I miss a place that contains information > > about that revision? > > Does tp-link offer separate images?
Eh, too obvious. Yes, there are separate images, also huge "GPL" tarballs for both. Inspecting firmware images suggests the differences aren't that big. One thing caught my eye in the kernel images: -console=ttyS0,115200 root=31:2 rootfstype=squashfs init=/sbin/init mtdparts=ath-nor0:128k(u-boot),1024k(kernel),6912k(rootfs),64k(config),64k(art) mem=64M +console=ttyS0,115200 root=31:2 rootfstype=squashfs init=/sbin/init mtdparts=ath-nor0:128k(u-boot),1024k(kernel),6912k(rootfs),64k(config),64k(art) mem=32M So it might just be a reduced-memory system but otherwise odds are good. Next steps when trying to play safe probably were * locate the serial connectors (the photos weren't helpful, sorry) * Build an openwrt image to be run from memory, for https://wiki.openwrt.org/doc/howto/generic.flashing#install_a_ramdisk-image_into_main_memory * See what going to happen. Unfortunately, this is a bit beyond the amount of time I can easily spare. Is there a document about "How to probe a new device for openwrt support" so I can avoid the worst gotchas? Christoph _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
