ucom.ko and palm pilot m500

[Anish Mistry]

On Friday 06 January 2006 01:56 pm, Carsten Wald wrote:
> 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.
You shouldn't be using usbd/usbd.conf as it is going away (It's 
already gone in CURRENT).  You should configure it using 
devd/devd.conf instead.


-- 
Anish Mistry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060106/646dcc4e/attachment.bin