Date: Sat, 13 Sep 2008 18:00:59 +0200 From: Ed Schouten <ed@80386.nl> To: Hans Petter Selasky <hselasky@c2i.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: mpsafetty and [missing] multi put char Message-ID: <20080913160059.GM1191@hoeg.nl> In-Reply-To: <200809131715.36017.hselasky@c2i.net> References: <87fxot5hoi.fsf@kobe.laptop> <20080826160144.GG99951@hoeg.nl> <200809131715.36017.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--AA9g+nFNFPYNJKiL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello hps, * Hans Petter Selasky <hselasky@c2i.net> wrote: > Maybe I've overlooked something, but why is there no multi put char funct= ion.=20 > Isn't looping over "tty_putchar(struct tty *tp, char c)" really slow when= =20 > receiving 70-80kbyte per second? tty_putchar() is not the routine that is called when receiving data. tty_putchar() does exactly the same thing as what `tputchar()' used to do, namely print a system message to the TTY. The routines you are probably looking for, are ttydisc_rint(), ttydisc_can_bypass() and ttydisc_rint_bypass(). Please take a look at http://wiki.freebsd.org/TTYRedesign how to use them. Good luck! --=20 Ed Schouten <ed@80386.nl> WWW: http://80386.nl/ --AA9g+nFNFPYNJKiL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkjL47sACgkQ52SDGA2eCwWZ7gCfaCkPSY//Q+OHgpJUDus8y4TX Vu8An1kF53mKTyAlYkOuYrgTaDeNZyI+ =q4AU -----END PGP SIGNATURE----- --AA9g+nFNFPYNJKiL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080913160059.GM1191>