--tThc/1wpZn/ma/RB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 12, 2005 at 03:31:35PM +0200, Quentin Garnier wrote:
> On Thu, May 12, 2005 at 11:39:27AM +0100, Nick Hudson wrote:
>=20
> While reading the code, though, I was wondering how difficult it would
> be to have an ucom(4) attaching to this device instead of mostly
> replicating all the code.  AFAICT, it should be possible to do that by
> adding a few methods to ucom_methods and making ucom(4) use them
> instead of making calls to usbd_* at the relevant places.
>=20
> That would save you a lot of documentation as to where to find the
> relevant device node, at least ;)
>=20
> Of course, I'm really no expert of the USB code, so I might be missing
> something.

I too have to ask why not have this attach as some sort of ucom. I know
very little about the USB code, but as a naive user, I'd expect a
USB<->Serial thingie to use the ucom device node. :-) So if you can do it,=
=20
please do. :-)

Take care,

Bill

--tThc/1wpZn/ma/RB
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFCg4ZgWz+3JHUci9cRAupFAJ0QpoS4Nz5ATm87reFPjZfjapn8aQCfQ5TV
Vj38W9UtikSTfyuWi8ys6jg=
=rEqj
-----END PGP SIGNATURE-----

--tThc/1wpZn/ma/RB--