From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Mackerras <paulus@samba.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@muc.de>,
Hugh Dickens <hugh@veritas.com>,
Michael Ellerman <michael@ellerman.id.au>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 5/6] From: Andrew Morton <akpm@osdl.org>
Date: Tue, 03 Oct 2006 17:25:51 +1000 [thread overview]
Message-ID: <1159860351.5482.49.camel@localhost.localdomain> (raw)
In-Reply-To: <20061003002014.321f68b6.akpm@osdl.org>
> yup, that fixed it. xmon apparently doesn't know where fbcon's output
> cursor is, but the characters are now readable.
The low level text engine used by xmon (and my some early console/debug
stuff on powerpc as well) really doesn't have any link to fbcon... doing
that would be hard and ugly and take the risk of making it fragile,
which isn't what we want to do... usually, when you fall into xmon, you
don't care about your console cursor :) (In fact, that stuff can even
blast on top of X if the later has the UseFBDev option).
Ben.
next prev parent reply other threads:[~2006-10-03 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061003010842.438670755@goop.org>
[not found] ` <20061003010933.392428107@goop.org>
2006-10-03 4:23 ` [PATCH 5/6] From: Andrew Morton <akpm@osdl.org> Paul Mackerras
2006-10-03 4:33 ` Andrew Morton
2006-10-03 5:19 ` Paul Mackerras
2006-10-03 5:50 ` Andrew Morton
2006-10-03 6:55 ` Paul Mackerras
2006-10-03 7:20 ` Andrew Morton
2006-10-03 7:25 ` Benjamin Herrenschmidt [this message]
[not found] ` <20061003010930.971200285@goop.org>
2006-10-03 10:37 ` [PATCH 1/6] Generic implemenatation of BUG Andi Kleen
2006-10-03 15:53 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1159860351.5482.49.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox