Re: Palm (Zire) and /dev/ucom0 on 6.0

2005-12-28 Thread DW

Igor Robul wrote:


On Tue, Dec 27, 2005 at 11:58:00AM -0500, DW wrote:
 


I then type:
# pilot-xfer -p /dev/cuaU0 -b backup

and I get:

  Listening to port: /dev/cuaU0
 
  Please press teh HotSync button now
   


Works fine for me with Palm TE2. You need press HotSync button and wait
a little.
 


Are you pressing HotSync before or after pilot-xfer?

If I do pilot-xfer first, then it fails because /dev/cuaU0 doesn't exist 
yet.


If I hit HotSync first, /dev/cuaU0 gets created, but then pilot-xfer 
tells me to hit HotSync, which I already did.
pilot-xfer just sits there waiting for Hotsync (already running), then 
HotSync on my Palm eventually times out and /dev/cuaU0 gets destroyed.





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

 



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Palm (Zire) and /dev/ucom0 on 6.0

2005-12-27 Thread DW

Jonathan Chen wrote:


On Fri, Dec 23, 2005 at 12:15:11PM -0500, DW wrote:

[...]
 

I do all this on my new 6.0 machine. When I hit the sync button on zire, 
I get the expected dmesg output (detecting the palm device), but there 
is no /dev/ucom0 device in /dev. Why?
   



Aside from adding uvisor, you don't have to change any other
configuration files for 6.0; the USB tty support files have changed
from /dev/ucom* in 5.0 to /dev/cuaU* in 6+.

Cheers.
 


Thanks.

I tried this, but am still having no luck syncing either through Jpilot 
interface or directly at console using pilot-xfer.


When I hit the hotsync button on my Zire, I get:

ucom0: PalmOne, Inc. Palm Handheld, rev 1.00/1.00, addr 2
ucom0: PalmOne, Inc. Palm Handheld, rev 1.00/1.10, addr 2

I then type:
# pilot-xfer -p /dev/cuaU0 -b backup

and I get:

   Listening to port: /dev/cuaU0
  
   Please press teh HotSync button now



then *nothing*

either I cancel on my zire, or it times out, and my dmesg output:

ucom0: ucomreadcb: IOERROR
ucom0: at uhub1 port2 (addr 2) disconnected
All threads purged from cuaU0
All threads purged from ttyU0
ucom0: detached


Of cource if I try to pilot-xfer the same command above *before* 
hitting hotsync on the zire, I get:


   The device /dev/cuaU0 does not exist..
   Possible solution:
 
  mkdnod /dev/cuaU0 c major minor


   Unable to bind to port: /dev/cuaU0


I'm doing all of this as *root* right now, just to get this working 
before I tackle the usual permissions issues that crop up when I do this 
as my regular user.


For laughs and giggles, I also tried all of this with /dev/ttyU0 as 
well, but it doesn't seem to make any difference.



Thanks for any help.

-DW
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Palm (Zire) and /dev/ucom0 on 6.0

2005-12-27 Thread Igor Robul
On Tue, Dec 27, 2005 at 11:58:00AM -0500, DW wrote:
 I then type:
 # pilot-xfer -p /dev/cuaU0 -b backup
 
 and I get:
 
Listening to port: /dev/cuaU0
   
Please press teh HotSync button now
Works fine for me with Palm TE2. You need press HotSync button and wait
a little.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Palm (Zire) and /dev/ucom0 on 6.0

2005-12-23 Thread DW

Hello all,

Has something changed in release-6.0 that affects usb communication with 
a palm/zire?


Here is what I have done from 5.2.1-5.4 to get my zire to sync with Jpilot:

1. add to my kernel:
device   ucom
device   uvisor

2. Add to /etc/defaults/devfs.rules:
[devfsrules_palm=100]
add path 'ucom*' group operator mode 0666

3. Add to /etc/rc.conf
devfs_enable=YES
devfs_system_ruleset=devfsrules_palm



I do all this on my new 6.0 machine. When I hit the sync button on zire, 
I get the expected dmesg output (detecting the palm device), but there 
is no /dev/ucom0 device in /dev. Why?


Does anybody know what I need to do or can you point me to the docs that 
will explain this to me?


Thanks a bunch,
DW

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Palm (Zire) and /dev/ucom0 on 6.0

2005-12-23 Thread Jonathan Chen
On Fri, Dec 23, 2005 at 12:15:11PM -0500, DW wrote:

[...]
 I do all this on my new 6.0 machine. When I hit the sync button on zire, 
 I get the expected dmesg output (detecting the palm device), but there 
 is no /dev/ucom0 device in /dev. Why?

Aside from adding uvisor, you don't have to change any other
configuration files for 6.0; the USB tty support files have changed
from /dev/ucom* in 5.0 to /dev/cuaU* in 6+.

Cheers.
-- 
Jonathan Chen [EMAIL PROTECTED]
--
  Opportunities are seldom labeled
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]