On Thu, Feb 26, 2009 at 01:33:36AM +0530, Shivdas Gujare wrote: > Hi Sarah, > > I tested my mobile MotorokrE6 with acting as a modem using cdc-acm driver. > and here is the result, I pasted. > http://pastie.org/399875 > > I believe, "rm: cannot remove > `/etc/udev/rules.d/025_usb-autosuspend.rules': No such file or > directory", can be avoided for first time user using "rm $UDEV_RULE" > in vid-pid-to-udev-rule.sh > Please, comment. Yes, I should check whether that file exists before trying to delete it. That line is only for regenerating rules after the script has been run a couple times. I'll fix it. > Also, "Type enter once you are actively using the device:", does this > wait for user to resume this device. I resumed my device using "echo > AT > /dev/ttyACM0" Yes, the tool is waiting for you to resume the device. Echoing to a tty device is a valid way to resume the device. You could also open minicom or a similar terminal emulator. > What is the meaning of "Does this device still work? (y/n):", how can > I make sure? When I was testing USB to serial devices, I made sure I could send characters both way with minicom. My friend who was testing a USB camera made sure it worked after resume by opening the device with the "cheese" program. Basically the prompt is asking if the device is behaving the way you expect it (like the printer still prints, your mouse still responds to movement, etc.). Is there a better way I could phrase that question? > Rest of the things worked fine. But I am not able to invoke > auto-generated udev-rule every time, I disconnect and reconnect the > device. I tried to debug this, and I can manually invoke udev-rule by > using "sudo udevadm trigger". > > This could be my machine's udev's problem? Oh, right. It's not your computer's fault. The script needs to tell udev to reload and re-read the rules. I'll fix that. Sarah > On Wed, Feb 25, 2009 at 4:35 AM, Sarah Sharp > <sarah.a.sharp@xxxxxxxxxxxxxxx> wrote: > > A couple months ago, I started on a tool to automatically test and enable > > automatic power management for USB devices. The USB Power Management tool (USB > > PM tool) is now mostly complete, and is available for download: > > > > git clone git://git.moblin.org/usb-pm-tool.git > > > > I would love for people to start testing USB devices with this tool. I haven't > > yet found any devices that can't handle selective suspend, so I really need > > testers with broken USB devices. > > > > If you run the tool and test a couple devices, please send me these two files: > > > > /etc/usb-pm-tool/pm-enabled-devices.txt > > /etc/usb-pm-tool/pm-broken-devices.txt > > > > > > About the tool: > > ============== > > > > The script usb-pm-tool.sh will present the user with a list of devices on their > > system that are capable of auto-suspend. The user picks a device to test, > > follows the prompts on the screen, and reports whether the device works > > successfully after the auto-suspend test. > > > > If the device passes the test, the script will prompt the user if they always > > want to enable auto-suspend for this device. If so, the script will generate a > > udev rule to enable auto-suspend for the device whenever it is plugged in. > > Enabling auto-suspend will lower system power consumption, but only if *all* the > > USB devices on the system have auto-suspend enabled. > > > > Eventually I want the tool to ask the user if they want to send info about their > > device to a centralized server. Then people could download the latest list of > > devices that correctly auto-suspend. That's still work in progress. > > > > Thanks for testing! > > > > Sarah Sharp > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
