LN52B750

[arris69]

Anyone have any idea what I should do differently based on the above dmesg output to get the vusb to do the right thing so the samba directories mounted inside showup under the device.

Thanks

GP

your dmesg looks ok, we don't use the virtual usb as mount point, we need it just let exeDSP think we have a real usb-storage device plugged to tv so
exeDSP beginn to monitor the file /dtv/usb/log.

arris

ps: i wait for output of

Code: Select all

sh -x /mtd_rwarea/SamyGo.sh

[arris69]

Do you know how they setup DEVPATH

...

GP

DEVPATH is set by /sbin/hotplug
it set up the env for hotplug scripts like:

Code: Select all

<4>block
<4>ACTION=add
<4>HOME=/
<4>SEQNUM=2
<4>MAJOR=8
<4>DEVPATH=/block/sda
<4>SUBSYSTEM=block
<4>PATH=/sbin:/bin:/usr/sbin:/usr/bin
<4>PHYSDEVPATH=/devices/platform/dummy_hcd/usb5/5-1/5-1:1.0/host0/target0:0:0/0:0:0:0
<4>MINOR=0
<4>PHYSDEVDRIVER=sd
<4>PWD=/
<4>PHYSDEVBUS=scsi

have you tried the "SamyGO All Extensions"? do the extensions work in your enviroment?

arris

[arris69]

I have not tried the extensions directly. Most of my scripts came from reading the extensions code. I am just being paranoid but I want to make sure I am writing the code just to be sure I understand what all I am changing. I guess here is my main question about making this work.

So there is a vusb block device which is all 0's so doesn't actually get mounted and two entries in the /dtv/usb/log.

Now my understanding is that
1) The loading of the kernel modules causes the device to show up in kernel which causes a hot plug event

correct

2) This causes some samsung code to put an entry in /dtv/usb/log for what needs to be mounted

wrong, /sbin/hotplug calls one of the hotplug-scripts/programs (guess from /mtd_boot/usb*)
this prog/script call /mtd_boot/usb_mount or /sbin/usb_mount, than the device will be mounted and an entry will be written
to /dtv/usb/log.
this was the first part, the second is
exeDSP monitors /proc/bus/usb or triggered also from hotplug , if a new usb-device are detected exeDSP beginns to
monitor /dtv/usb/log and/or /dtv/usb/netlog (depends on hotplug event block or net)

3) Some other samsung script reads the /dtv/usb/log to figure out what all to show in media.p setup

exeDSP reads /dtv/usb/*log and show you a notification if the file is changed (usb-storage or usb-network)

Now my question is that:
1) Does 3 happen only when you actually press the media.p button and go to devices?

no, before.

2) If not and if it happens as soon as the hot plug event is detected, then how do we know that we get the second entry into /dtv/usb/log in time (because there is a 3 second sleep after the last module load)?

important is than you write to /dtv/usb/log after exeDSP means there is an usb-storage device plugged in.

you can test it, attach an usb-pen to tv (exit from notification window), than write entries to /dtv/usb/log (you know the syntax ) notification
window should come again (but don't write same entry again, you have to change the MountDir may other things too, double entries are ignored)
you also can reset the media.p list with

Code: Select all

echo > /dtv/usb/log

hth
arris