--4WCkKXOGtgJBEb9G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 25, 2006 at 03:17:32AM -0400, Jeremy Tregunna wrote:
> I recently purchased a Kingston USB->IrDA adapter for use with =20
> another device I own here, and NetBSD sees it as a ugen(4) device. I =20

=2E.. which means it is not recognised by the uirda driver.

> installed comm/birda from pkgsrc, but I get errors that ircomm cannot =20
> open /dev/irframe0. If I try and change the device to irframe1, same =20
> deal. Permissions are fine, so I'm presuming a problem with the =20
> communication between the device and the kernel. Attached is the =20
> dmesg output.

Please give usbdevs -v output.  But if doesn't expose itself as an IrDA
device I wouldn't have much hope.  FWIW, the Linux drivers doesn't match
any device our uirda(4) doesn't.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--4WCkKXOGtgJBEb9G
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iQEVAwUBRO7IAtgoQloHrPnoAQKxsAf+PEb0vNUYICxBVfNt60bjg3b/H+DdWO9w
0ZH5lmMB5T+Ss+QwyX+cyrDUJvP0vKLIiTld4iqi9s1SqKFEdAd+AvyunL1mIrRu
34vX/0Mm78u2lDTuUur5Dv9q6Da02Elx9aNqfmklI8s7jzBCTfZKrNCtdzNToKrO
qwvD60uhRhZLOrQrbDsCg/Cgc8CPOQWMCKunLopUpmh9beVChOdNAjrOiW6wIPrh
7OOYx9et3AcFYC1uaZs/zoLbfKh0zZoiWITgjcCdmCzOgVjxiRo1fVBHsPPwH/RO
jRYVYhoy/9tC50mtZ+SYC16S6obJ87Lbe1vG89VJfqLURiLNzpzmBw==
=6Kxk
-----END PGP SIGNATURE-----

--4WCkKXOGtgJBEb9G--