From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Daniel Hazelton <dhazelton@enter.net>,
"H. Peter Anvin" <hpa@zytor.com>,
Kyle Moffett <mrmacman_g4@mac.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Albert Cahalan <acahalan@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
aeb@cwi.nl
Subject: Re: console font limits
Date: Fri, 4 May 2007 08:34:40 -0700 [thread overview]
Message-ID: <200705040834.41000.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1178254748.4722.4.camel@daplas>
On Thursday, May 03, 2007, Antonino A. Daplas wrote:
> On Thu, 2007-05-03 at 23:58 -0400, Daniel Hazelton wrote:
> > On Thursday 03 May 2007 20:39:05 H. Peter Anvin wrote:
> > > Kyle Moffett wrote:
> >
> > I guess I could start on that work again - shouldn't take me all that
> > long to recover the stuff I lost when a blackout caused my hard drive
> > to get corrupted beyond recovery (and the automated journal replay
> > didn't do a damned thing - I think it actually *added* to the
> > corruption, but I don't think any filesystem would have survived that)
>
> You might want to look at the modesetting-101 branch of DRM. It's goal
> is similar to yours. They even have a drm framebuffer. I don't know
> how far they are with their goal, but I can see some progress.
>
> Here's their git tree:
>
> git://git.freedesktop.org/git/mesa/drm#modesetting-101
It sounds like we'll need a new KD_* flag for this work too, something like
KD_TEXT_BUT_ONLY_ON_PANIC, sine with the above tree, the kernel will have
intimite knowledge of the current graphics mode, framebuffer location,
etc. It should be enough to clear the scanout buffer and output the
printk, though if there's a lot of rendering going on, the DRM driver
might have to be pretty smart about it.
Jesse
next prev parent reply other threads:[~2007-05-04 15:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 4:09 console font limits Albert Cahalan
2007-05-01 11:49 ` Geert Uytterhoeven
2007-05-01 12:11 ` Antonino A. Daplas
2007-05-01 15:05 ` H. Peter Anvin
2007-05-01 15:49 ` Albert Cahalan
2007-05-02 18:02 ` Jan Engelhardt
2007-05-03 6:17 ` Albert Cahalan
2007-05-03 7:12 ` Jan Engelhardt
2007-05-03 14:14 ` Albert Cahalan
2007-05-03 14:26 ` Jan Engelhardt
2007-05-03 15:56 ` Geert Uytterhoeven
2007-05-03 18:27 ` Jan Engelhardt
2007-05-03 20:15 ` H. Peter Anvin
2007-05-03 20:16 ` Jan Engelhardt
2007-05-04 0:17 ` Kyle Moffett
2007-05-04 0:39 ` H. Peter Anvin
2007-05-04 3:58 ` Daniel Hazelton
2007-05-04 4:59 ` Antonino A. Daplas
2007-05-04 15:34 ` Jesse Barnes [this message]
2007-05-06 23:35 ` Daniel Hazelton
2007-05-03 7:19 ` H. Peter Anvin
2007-05-03 7:45 ` Helge Hafting
2007-05-03 10:20 ` Alan Cox
2007-05-01 17:06 ` Ken Moffat
2007-05-03 17:11 ` Andries Brouwer
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=200705040834.41000.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=acahalan@gmail.com \
--cc=adaplas@gmail.com \
--cc=aeb@cwi.nl \
--cc=dhazelton@enter.net \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.