Date: Fri, 6 Jan 2006 18:56:32 +0000 From: Carsten Wald <carsten@betaversion.net> To: freebsd-stable@freebsd.org Subject: Re: ucom.ko and palm pilot m500 Message-ID: <200601061856.32626.carsten@betaversion.net> In-Reply-To: <000501c612e9$c57b2620$0130a8c0@Gleb> References: <200601061643.15259.carsten@betaversion.net> <000501c612e9$c57b2620$0130a8c0@Gleb>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 06 January 2006 17:51, Gleb Kozyrev wrote: > man uvisor Great! Thank you. That's what I needed! -- uvisor.ko apparently uses ucom.ko and the ucom0 device I looked for is (temporarily) created. However, after pressing the sync button the pilot can then be accessed through the /dev/ttyU0 device. Since I didn't find this information at kpilot.org or pilot-link.org or whatsoever (although they oftern refer to FreeBSD) and somebody else might have the same problem ... here is what I did: 1. Load the proper kernel modules. Among others this is uvisor.ko. $ kldload /boot/kernel/uvisor.ko (In addition, I configured this in /boot/loader.conf) 2. Configure /etc/usbd.conf in such a way, that the permissions of the proper device will be set when it appears after pressing the HotSync button. This is /dev/ttyU0 in my case. I just synced as a normal user and it works. -- bye Carsten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601061856.32626.carsten>