[OpenWrt-Devel] [PATCH] ramips: add support for Intenso Memory 2 Move USB 3.0

John Crispin blogic at openwrt.org
Sat Jan 17 09:09:24 EST 2015

On 17/01/2015 14:49, Christian Lamparter wrote:
> On Saturday, January 17, 2015 07:48:24 AM John Crispin wrote:
>> On 15/01/2015 22:47, Christian Lamparter wrote:
>>> This adds support for a rt5350-based "portable nas" solution
>>> from Intenso. The board comes with 32M RAM and 8M Flash, the
>>> built-in HDD is connected/accessible via a usb3.0<->sata
>>> bridge VLI VL701.
> BTW: In the meantime, I was able to find the Chinese distributor
> for this product. The devices seem to be sold by "IOVST" and
> they call it the "UIS700HD" [0]. 
> However, this might not be the hardware vendor. The RT2860.bin in
> the rootfs has ApCliSsid set to "Tenda_501500". But I haven't
> found anything remotely close on Tenda's product website. 
> my question is: should I rename the profile (and the files) to:
> UIS700HD then?
> I would like to keep the Intenso name, because they provided 
> me/us/anyone with at least a (partially very useful)
> "GPL source" for their product on their website [1].

feel free to leave it as intenso, just make sure to add a wiki page and
list the alternative SKUs there.

> The HDD was originally formatted with a single 500GB (size of the HDD) 
> vfat[FAT32] partition. The original firmware supports vfat, exfat (via
> fuse), ntfs (via tuxera tntfs module) and ext2 (ext2 is used exclusively
> for updating the device firmware. It might be only available for the
> ramdisk uimage?! see notes about upfs [2]).
> The rootfs has a few traces of additional support [i.e.: they are
> listed in scripts or have installed fstools] for hfsplus and xfs.
> But as far as I can tell, they won't work.
> BTW: I would like to generate a ramdisk image by default too 
> (I was thinking of adding FEATURES+=ramdisk). The reason is
> that this would make flashing the device easier (load the
> ramdisk image via tftp and then use sysupgrade with the
> squashfs-sysupgrade image).

feel free to send a patch.

applied your patch as r44001

> However, this would of course cause all other rt305x devices
> to build the ramdisk too! [which is probably not ideal. So, 
> is there another way?]. 
> Regards,
> Christian
> [0] <http://www.iovst.com/product/article-41.html>
> [1] <http://www.intenso.de/downloads.php?kategorie=29&&produkt=1357297608>
> [2] <http://hckohwnotes.blogspot.de/2014/05/debian-on-intenso-memory-2-move-intenso.html>
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list