On Thu, 2010-01-14 at 12:42 +0100, Bernd Petrovitsch wrote: > On Mit, 2010-01-13 at 19:05 -0300, Diego Woitasen wrote: > > Hi, > > I want to clear the console before a printk() call. Is there a > > funcion in the kernel API to do it? > No, because "the console" can be your ordinary Linux console or over the > network or over a serial line. > You could look up the control character which clears terminals and plain > simply emit that (and the output device should behave accordingly) but I > won't do that in any case because I don't see any reason why one wants > to hide kernel messages coming out on a/the console - most of them > indicate pretty serious errors (or situations) and the last thing one > wants is to hide them. > > Bernd Hi Bernd, Considering your advice : > No, because "the console" can be your ordinary Linux console or over the > network or over a serial line. I can't seem to find any reference to getting *both* the "ordinary" AND the serial line to work. (As is my case with the HID keyboard - I need console input from the kdb driver + my existing ttyS0 serial line...) For group : This is not some lazy question - I've really done my homework on this one. I don't mind that because the initial goal is to learn the kernel more and more. In fact, however, I'm a bit stumped that despite providing a concise description of the problem, and substantiating where I'm stuck, there is no help whatsoever. I frequently see "one or two liner questions" (which are considered quite rude on many groups I frequent), but yet they result in a plethora of responses. Can anyone advise what I'm doing wrong (in posting), so I can get someone to get me back on track ??? As in my last conclusion, it seems that something is going awry in the console binding. (USB HID keyboard -> tty bind). Perhaps I'm overlooking something about that ? (CMIIW, but I haven't provided the kernel config, as that seems peripheral issue) -- Best regards, Kris -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
