Hi Ben,
--- Benjamin Herrenschmidt <[EMAIL PROTECTED]>
escribió:
> Yes. We discussed that with Linus back then. The
> problem is that the
> printk subsystem tend to abuse calling low level
> drivers at interrupt
> time, and in the case of blanking/unblanking, this
> can be a problem.
> Radeonfb
On Thu, 2005-07-14 at 13:38 +0200, Jan Engelhardt wrote:
> >Before 2.6.12-rc2, the console was unblanked by just
> >writing to the console.
> >For keyboardless and mouseless systems (which is my
> >case, embedded) this new behaviour is a bit annoying.
>
> Interesting. I have observed the
>
> I have this problem since 2.6.12-rc2.
> If I add back the patch hunk specified in my original
> message, the blanking behaviour changes to that
> present in pre-2.6.12-rc2 kernels.
And you'll have nice scheduling in atomic for any printk() done in
atomic context that triggers the unblank()
On Thu, 2005-07-14 at 01:12 +0200, Albert Herranz wrote:
> Hi,
>
> Looks like, since [1] was merged, a blanked console
> (due to inactivity for example) doesn't get unblanked
> anymore when new output is written to it.
>
> This hunk of the already metioned patch, which
> modifies
On Thu, 2005-07-14 at 01:12 +0200, Albert Herranz wrote:
Hi,
Looks like, since [1] was merged, a blanked console
(due to inactivity for example) doesn't get unblanked
anymore when new output is written to it.
This hunk of the already metioned patch, which
modifies vt_console_print() in
I have this problem since 2.6.12-rc2.
If I add back the patch hunk specified in my original
message, the blanking behaviour changes to that
present in pre-2.6.12-rc2 kernels.
And you'll have nice scheduling in atomic for any printk() done in
atomic context that triggers the unblank() when
On Thu, 2005-07-14 at 13:38 +0200, Jan Engelhardt wrote:
Before 2.6.12-rc2, the console was unblanked by just
writing to the console.
For keyboardless and mouseless systems (which is my
case, embedded) this new behaviour is a bit annoying.
Interesting. I have observed the following
Hi Ben,
--- Benjamin Herrenschmidt [EMAIL PROTECTED]
escribió:
Yes. We discussed that with Linus back then. The
problem is that the
printk subsystem tend to abuse calling low level
drivers at interrupt
time, and in the case of blanking/unblanking, this
can be a problem.
Radeonfb for
>Before 2.6.12-rc2, the console was unblanked by just
>writing to the console.
>For keyboardless and mouseless systems (which is my
>case, embedded) this new behaviour is a bit annoying.
Interesting. I have observed the following (2.6.13-rc1 and a little
earlier):
mplayer bla.avi -vo cvidix
Hi,
--- Jan Engelhardt <[EMAIL PROTECTED]>
escribió:
> The console is unblanked when you hit a key (or
> probably move a mouse too),
> not when some application outputs something on
> stdout/stderr/etc.
Before 2.6.12-rc2, the console was unblanked by just
writing to the console.
For
>Looks like, since [1] was merged, a blanked console
>(due to inactivity for example) doesn't get unblanked
>anymore when new output is written to it.
The console is unblanked when you hit a key (or probably move a mouse too),
not when some application outputs something on stdout/stderr/etc.
Looks like, since [1] was merged, a blanked console
(due to inactivity for example) doesn't get unblanked
anymore when new output is written to it.
The console is unblanked when you hit a key (or probably move a mouse too),
not when some application outputs something on stdout/stderr/etc.
[1]
Hi,
--- Jan Engelhardt [EMAIL PROTECTED]
escribió:
The console is unblanked when you hit a key (or
probably move a mouse too),
not when some application outputs something on
stdout/stderr/etc.
Before 2.6.12-rc2, the console was unblanked by just
writing to the console.
For keyboardless and
Hi,
Looks like, since [1] was merged, a blanked console
(due to inactivity for example) doesn't get unblanked
anymore when new output is written to it.
This hunk of the already metioned patch, which
modifies vt_console_print() in drivers/char/vt.c, is
possibly the cause:
@@ -2220,9 +2220,6 @@
Hi,
Looks like, since [1] was merged, a blanked console
(due to inactivity for example) doesn't get unblanked
anymore when new output is written to it.
This hunk of the already metioned patch, which
modifies vt_console_print() in drivers/char/vt.c, is
possibly the cause:
@@ -2220,9 +2220,6 @@
15 matches
Mail list logo
