Subject: Re: com on bluetooth
To: Iain Hibbert <plunky@rya-online.net>
From: Daniel Carosone <dan@geek.com.au>
List: tech-userlevel
Date: 01/24/2007 13:58:09
--jQIvE3yXcK9X9HBh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 23, 2007 at 09:21:49PM +0000, Iain Hibbert wrote:
> I found why this happens in stdio mode. Because of the tty input
> processing, no <cr> ever gets transmitted..
>=20
> Then I found another problem. The slave tty was being set to raw mode and
> probably it was this that made the 'cu -l ttyp9' fail to work properly..

Great!  Both of these seem to work now, in quick first testing.

> So, in the process of adding a server mode I've mostly rewritten
> rfcomm_sppd.c, new version and manpage is attached.. Please take a look
> and let me know if you can get it to work* with pppd?  I'm not sure how to
> go about setting that up with only one machine so I haven't tried it, but
> plain connections work just fine as do outgoing PPP connections.

I'll get around to testing this part a little later, thanks again.

--
Dan.

--jQIvE3yXcK9X9HBh
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFFtstAEAVxvV4N66cRAvryAKCvFU6741ndjlO3hmEvRrrr747KCACeNNk6
9EgpvWxu1n7/F0rbJO732Pk=
=lLeT
-----END PGP SIGNATURE-----

--jQIvE3yXcK9X9HBh--