Was the below information helpful? Also, I have access to a variety of hardware. I am not sure how to get to the sub-vendor sub-id information on the ar71xx platform when OpenWrt is loaded. The 'lspci' command pciutils reports nothing. I got the Pico M2 value from AirOs (which is not usually loaded on the devices I have access to. Please advise.
On 20 February 2012 23:46, Hanno Schupp <hanno.sch...@gmail.com> wrote: > I assume you want mtd5: > > root@Router002722400:~# cat /proc/mtd > dev: size erasesize name > mtd0: 00040000 00010000 "u-boot" > mtd1: 00010000 00010000 "u-boot-env" > mtd2: 00100000 00010000 "kernel" > mtd3: 00660000 00010000 "rootfs" > mtd4: 00410000 00010000 "rootfs_data" > mtd5: 00040000 00010000 "cfg" > mtd6: 00010000 00010000 "EEPROM" > mtd7: 00760000 00010000 "firmware" > > Here goes... > > On the UBNT images: I have reported the same observation a few weeks > ago - with no reaction. How should to best submit the information? > > > On 20 February 2012 23:31, Jo-Philipp Wich <x...@subsignal.org> wrote: >>> No, it does not yet, but it may not look for them yet either - after >>> all there is nothing in the code for Picos until now. >> >> It is supposed to find them, even if there is no entry in the hardware >> table - so something is broken on this particular model. >> >> Would it be possible for you to seen me a copy of the boardconfig >> partition? (Lookup the mtd index in /proc/mtd and dump it with dd >> if=/dev/mtdblockX of=/tmp/boardconfig.bin) >> >>> There is also no specific image for the Pico M created - just for >>> Nano M, Rocket M and Bullet M. There is also no image for the Loco M >>> created, although it would be worthwhile, as it has a different >>> maximum power (23dBm) compared to the Nano M (28dBm), and it has only >>> one Ethernet jack (eth0),as opposed to the Nano M, which has two >>> (eth0 and eth1 work), but for the Nano M the default configuration in >>> OpenWrt does not even define eth1 from the start. Something that >>> could be fixed? >> >> It is probably worth fixing but outside of the scope here. >> >> ~ Jow >> _______________________________________________ >> 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
