From: Stephen W. <sa...@us...> - 2004-02-24 16:47:30
|
On Tue, 2004-02-24 at 00:35, Roger Binns wrote: > > I made a version of sendpbcommand in com_sanyo5500 that seems to get > > around timeouts. I simply rewrite the output packet and wait for the > > reply again. This can work for the sanyo phones since there are no init > > and nextentry as there are for the LG phones. > > When you are happy with it, can you put it back in the main code for all > phones :-) Maybe add a safe to retry parameter to the routine which would > always be yes for Sanyo, and no for Brew and LG stuff? Are you proposing to merge sendbrewcommand, the LG sendpbcommand and the Sanyo sendpbcommand into one routine? They are all similar, so I guess that's possible. The Brew error reporting in sendbrewcommand should be safe for Phonebook calls since presumably there are no phonebook protocol packets starting with 0x59. Presumably I can also figure out how to bypass the sequence stuff in the LG sendpbcommand by testing to see if request.header.sequence exists. At any rate, there is stuff in the LG sendcommand, like CRC checking, that you added since I forked the Sanyo one that I should have in the Sanyo code. > > > E: Ad=8a(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > > E: Ad=0b(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms > > > > I think the Sanyo 5500 is also 64 characters. > > That is what it looks like for those endpoints. It doesn't quite explain > why Snoopy was claiming packets larger than that since that would be a > violation of the USB protocol. Is there anyther usb monitor program that you recommend other than snoopypro? Stephen |