Re: Treo 300: pilot-link works, gnome-pilot doesn't

["David A. Desrosiers" <hacker gnu-designs com>]

> Uh, yes.  From the same post you replied to:

	My bad, long weekend.

> Or you could have taken a quick glance at the attached patch.

	My mail is remote, having to save off the patch, close mail, vi the
patch, blah blah, etc. I trust the patch was attached, I can't try it right
now though, because I'm stuck debugging 100% reproducable machine hard
lockups with my Treo90.

	I can see lots of wonderful exploits happening with this code if it
doesn't get fixed quickly. I can walk up to a machine running hotplug (yet
another reason never to run it), plug in my Treo, hit HotSync, tap Cancel,
and immediately hard-lock the machine, all without ever having an account on
the box, just with a USB device plugged into the back. Niiiice.

> It does properly detect the device now (though as a Visor, not a Treo;
> since product_id is 0x0100 I don't see how we can distinguish...),

	Oddly, my Treo90 is 0200, and the rest appear to be 0100. Check the
pilot-link.org Wiki (wiki.pilot-link.org).

> Something else is wrong.

	Are you using Greg's rollup patches, or the other (non-working) ones
that have been floating around lately? I know Greg's latest on 2.4 stopped
the hard-lockups on my Thinkpad, but 2.5 still hard locks the box when I tap
Cancel on the Treo90 when it tries to sync. What kernel are you using again?


d.