dummy_hcd.ko for C-series T-VALDEUC

[arris69]

whats about add -o fsname xfs to fusesmb?
in SamyGO/etc/init.d/04_04_fusesmb.init change

Code: Select all

fusesmb $DEST_DIR

to

Code: Select all

fusesmb $DEST_DIR -o fsname=xfs

but this requires to write correct entry to /dtv/usb/usblog?

arris

[arris69]

...

I prefer NFS over smb or any fuse fs. NFS is already supported by the kernel.

the kernel supports whatever you load as module too

Something else.
Can you please explain what g_file_storage.ko does?

it maps a file as usb-storage device, so for the host it looks like you attached a usb-hdd/pen to the device. (http://www.linux-usb.org/gadget/)

hth
arris

[arris69]

/dev/loop0 is existent on every c-series?

what's if:
mount a writable network-share to /dtv/usb/test (cifs or nfs)
create 16MB xfs image on /mtd_rwcommon/pvrimage.img

Code: Select all

mkdir -p /dtv/usb/pvrdir
mount -t xfs /mtd_rwcommon/pvrimage.img /dtv/usb/pvrdir 

(wonder why -o loop isn't required?)

Code: Select all

ln -s /dtv/usb/test /dtv/usb/pvrdir/CONTENTS

or with mount -o bind, like:

Code: Select all

mkdir -p /dtv/usb/pvrdir/CONTENTS
mount -o bind /dtv/usb/test /dtv/usb/pvrdir/CONTENTS

and fake usability

Code: Select all

echo 1 > /dtv/usb/pvrdir/CONTENTS/.PVRPfmChkLog

arris

[arris69]

...

My plan is something similar. The 16MB XFS image will be rejected disregarding the .PVRPfmChkLog file. It seems to check the size first. We need to use a xfs prepared img of >1GB in a pre-mounted writable network share to get this working.

may somebody like to look into xfsprogs sources, maybe it's possible to create a small xfs image with a faked size (we really just need acces to a few blocks)
http://www.google.at/url?sa=t&source=we ... SQ&cad=rja

The unclear part for me is the mount -t xfs img. Why is this needed?

seems c series supports loop devices, so we can mount disk images on the fly. (may also iso images???)

I haven't got above plan working yet. Still have some odd behaviour. Perhaps this mount does the trick.

arris