Re: [PATCH] Stop printk printing non-printable chars

Jan-Benedict Glaw
2004-06-19T08:31:08Z

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

On Sat, 2004-06-19 01:03:30 +0100, matthew-lkml@newtoncomputing.co.uk <matthew-lkml@newtoncomputing.co.uk>
wrote in message <20040619000330.GC5286@newtoncomputing.co.uk>:
> On Fri, Jun 18, 2004 at 11:32:52PM +0200, Jan-Benedict Glaw wrote:
> > On Fri, 2004-06-18 21:53:55 +0100, matthew-lkml@newtoncomputing.co.uk <matthew-lkml@newtoncomputing.co.uk>
> > wrote in message <20040618205355.GA5286@newtoncomputing.co.uk>:

> > It's dandy if you pump out some data via serial link.
>
> Is printk ever used to send anything out via a serial link? I assumed it
> was only kernel log messages (that should really be fairly sane). Log
> messages sent to serial printer, etc, don't want dodgy chars in them
> that may mess up the printer, do they?

printk() is a printf() like interface to the log buffer. From there, all
console drivers are fed, and in development (not for office or private
use), you often attach a seruak cibsike to capture Oops messages and the
like.

MfG, JBG

--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]