Phil Dibowitz wrote: > On Sun, Mar 16, 2008 at 09:47:35PM -0700, Zach Carter wrote: >> Maybe the thing to do is just ignore the return code from >> usb_interrupt_write, and instead check that the same device (identify by >> serial number?) comes back online. > > In the meantime we'll ignore the return value of reset_remote() like the patch > posted earlier today. We definitely should, at some point, be checking the > remote comes back, but it hasn't been a huge priority for me.
I've committed a change that should apply the aforementioned fix. Thanks for your help! -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
