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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]