From: Pavel Machek <pavel@ucw.cz>
To: Dave Airlie <airlied@gmail.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, Adam Jackson <ajax@nwnk.net>,
Arjan van de Ven <arjan@infradead.org>,
Casey Dahlin <cjdahlin@ncsu.edu>,
linux-kernel@vger.kernel.org
Subject: Re: Overriding X on panic
Date: Wed, 29 Nov 2006 13:57:04 +0000 [thread overview]
Message-ID: <20061129135704.GB4769@ucw.cz> (raw)
In-Reply-To: <21d7e9970611261419s12da9881h1f19adcf11756769@mail.gmail.com>
Hi!
> >> for the Intel hw Keith doesn't seem to think it's all
> >that much of a
> >> problem though...
> >
> >Including the TV out, odder LCD panels, non BIOS modes
> >etc ? If so then
> >it might be an interesting test case for intelfb to
> >grow some kind of
> >console helper interface
...
> I personally think we need to probably just bite the
> bullet and start
> sticking graphics drivers into the kernel, the new
> randr-1.2 interface
> for X is probably a good starting point for a generic
> mode setting
> interface that isn't so X dependent and could replace
> fbdev with
> something more sane wrt dualhead and multiple outputs...
> fbdev could
> be implemented on top of that layer then.. also
> suspend/resume really
> needs this sort of thing....
Yes, pretty please...
> My main worry with integrating graphics drivers into the
> kernel is
> that when they don't work the user gets no screen, with
> network/sound
> etc this isn't so bad, but if they can't see a screen
> debugging gets
> to be a bit more difficult....
You can have my hgc card + monitor if it helps :-). Okay, it is old
ISA, so it probably does not, but with serial or netconsole debugging
should be doable, no?
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-11-29 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 5:54 Casey Dahlin
2006-11-25 8:32 ` Arjan van de Ven
2006-11-25 16:10 ` Alan
2006-11-26 2:48 ` Matthew Garrett
2006-11-26 8:18 ` Arjan van de Ven
2006-11-26 14:22 ` Alan
2006-11-26 22:19 ` Dave Airlie
2006-11-26 22:42 ` D. Hazelton
2006-11-29 13:57 ` Pavel Machek [this message]
2006-11-25 16:09 ` Alan
2006-11-26 12:40 ` James Courtier-Dutton
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=20061129135704.GB4769@ucw.cz \
--to=pavel@ucw.cz \
--cc=airlied@gmail.com \
--cc=ajax@nwnk.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=cjdahlin@ncsu.edu \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®