unsubscribe

[Dav <wdavfr numericable fr>]

On Mon, 2003-03-10 at 18:00, gnome-pilot-list-request gnome org wrote:
> Send gnome-pilot-list mailing list submissions to
> 	gnome-pilot-list gnome org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
> or, via email, send a message with subject or body 'help' to
> 	gnome-pilot-list-request gnome org
> 
> You can reach the person managing the list at
> 	gnome-pilot-list-admin gnome org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gnome-pilot-list digest..."
> 
> 
> Today's Topics:
> 
>    1. Treo 300: pilot-link works, gnome-pilot doesn't (Adam C Powell IV)
>    2. Re: Treo 300: pilot-link works, gnome-pilot doesn't (David A. Desrosiers)
>    3. Re: Treo 300: pilot-link works, gnome-pilot doesn't (Adam C Powell IV)
> 
> --__--__--
> 
> Message: 1
> Date: Mon, 10 Mar 2003 08:46:31 -0500
> From: Adam C Powell IV <hazelsct mit edu>
> Organization: Massachvsetts Institvte of Technology
> To: GNOME Pilot <gnome-pilot-list gnome org>
> Subject: Treo 300: pilot-link works, gnome-pilot doesn't
> Reply-To: gnome-pilot-list gnome org
> 
> Hello,
> 
> First, a success story: Adam Pennington's 2.4.20 patch at 
> http://munge.org/linux/linux-2.4.20-treo.patch (vs. 2.4.21-pre-5 at 
> http://lyre.mit.edu/~powell/debs/linux-2.4.21-pre5-treo.patch) makes the 
> Handspring Treo 300 work with pilot-xfer!  I can list the files just 
> fine now, but haven't tried any other pilot-xfer functions.  Greg K-H is 
> planning to merge it so it gets into 2.4.21.  Cool!
> 
> Unfortunately, syncing with gnome-pilot doesn't work.  The device 
> doesn't connect with the USB port until hotsync is actually pressed, so 
> before then, /dev/ttyUSB1 and 0 are dead, and when I "pilot-xfer" before 
> pressing hotsync, it says "no such device".
> 
> Funny thing is, if gpilotd is running and I push sync, the device hangs 
> and never times out.  If I then run pilot-xfer, it sees /dev/ttyUSB1 and 
> tries to start syncing, but *then* the device times out (and disconnects).
> 
> So I think something is wrong in gpilotd's assumptions about when things 
> will happen.  Perhaps it isn't monitoring /dev/ttyUSB1 like it says it 
> is, because there's no such device before sync?
> 
> How can I help debug?  .gnome-errors prints nothing unusual after I 
> press sync, neither is anything unusual in /var/log/kern.log...
> 
> One other thing: I haven't cleared out IDs since syncing with my old 
> pilot; do I have to create a new entry in the "Pilots" tab of the 
> capplet, or erase the "Sync PCId" from the "Advanced" tab?
> 
> TIA,
> -- 
> 
> -Adam P.
> 
> GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6
> 
> Welcome to the best software in the world today cafe! 
> <http://lyre.mit.edu/%7Epowell/The_Best_Stuff_In_The_World_Today_Cafe.ogg>
> 
> 
> 
> --__--__--
> 
> Message: 2
> Date: Mon, 10 Mar 2003 10:11:16 -0500 (EST)
> From: "David A. Desrosiers" <hacker gnu-designs com>
> To: gnome-pilot list <gnome-pilot-list gnome org>
> Subject: Re: Treo 300: pilot-link works, gnome-pilot doesn't
> Reply-To: gnome-pilot-list gnome org
> 
> 
> > Funny thing is, if gpilotd is running and I push sync, the device hangs
> > and never times out.  If I then run pilot-xfer, it sees /dev/ttyUSB1 and
> > tries to start syncing, but *then* the device times out (and disconnects).
> 
> 	What version of gnome-pilot are you using?
> 
> 	What version of pilot-link was it built against?
> 
> > So I think something is wrong in gpilotd's assumptions about when things
> > will happen.  Perhaps it isn't monitoring /dev/ttyUSB1 like it says it is,
> > because there's no such device before sync?
> 
> 	gnome-pilot doesn't read the Treo device info from /proc, because as
> you probably figured out, /proc/bus/usb/devices for these newer devices (OS5
> devices, Treo, etc.) do not have the string "Palm Handheld" in them as they
> did previously (gpilotd/gpilotd.c in struct product_names). This has to be
> patched to handle the lookups for the actual product_id and the vendor_id
> (in this case, 082d and 200 respectively). I think someone did this for the
> Tungsten awhile back on this list. You might want to search the archives.
> 
> 
> d.
> 
> 
> --__--__--
> 
> Message: 3
> Date: Mon, 10 Mar 2003 11:35:54 -0500
> From: Adam C Powell IV <hazelsct mit edu>
> Organization: Massachvsetts Institvte of Technology
> To: gnome-pilot-list gnome org
> Subject: Re: Treo 300: pilot-link works, gnome-pilot doesn't
> Reply-To: gnome-pilot-list gnome org
> 
> David A. Desrosiers wrote:
> 
> >>Funny thing is, if gpilotd is running and I push sync, the device hangs
> >>and never times out.  If I then run pilot-xfer, it sees /dev/ttyUSB1 and
> >>tries to start syncing, but *then* the device times out (and disconnects).
> >>    
> >>
> >	What version of gnome-pilot are you using?
> >
> >	What version of pilot-link was it built against?
> >
> 0.1.71-5 Debian woody backport, 0.11.7-2 backport.
> 
> >>So I think something is wrong in gpilotd's assumptions about when things
> >>will happen.  Perhaps it isn't monitoring /dev/ttyUSB1 like it says it is,
> >>because there's no such device before sync?
> >>    
> >>
> >	gnome-pilot doesn't read the Treo device info from /proc, because as
> >you probably figured out, /proc/bus/usb/devices for these newer devices (OS5
> >devices, Treo, etc.) do not have the string "Palm Handheld" in them as they
> >did previously (gpilotd/gpilotd.c in struct product_names). This has to be
> >patched to handle the lookups for the actual product_id and the vendor_id
> >(in this case, 082d and 200 respectively). I think someone did this for the
> >Tungsten awhile back on this list. You might want to search the archives.
> >
> Actually, the treo 300 is showing up as 082d and 0100, like a plain 
> Visor.  Here's what shows up in /proc/bus/usb/devices:
> 
> T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 12 Spd=12  MxCh= 0
> D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=082d ProdID=0100 Rev= 1.00
> C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=  2mA
> I:  If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=serial
> E:  Ad=01(O) Atr=02(Bulk) MxPS=   8 Ivl=0ms
> E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=1ms
> E:  Ad=03(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=84(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> 
> There's no "Palm" or "Handspring" anywhere, so no match to anything in 
> product_names.  Perhaps a more involved patch is required?  I'd be glad 
> to help...
> 
> Thanks,
> -- 
> 
> -Adam P.
> 
> GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6
> 
> Welcome to the best software in the world today cafe! 
> <http://lyre.mit.edu/%7Epowell/The_Best_Stuff_In_The_World_Today_Cafe.ogg>
> 
> 
> 
> 
> 
> --__--__--
> 
> _______________________________________________
> gnome-pilot-list mailing list
> gnome-pilot-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
> 
> 
> End of gnome-pilot-list Digest
-- 
Dav <wdavfr numericable fr>