From: Alex Deucher <alexdeucher@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
dri-devel@lists.sourceforge.net,
Paulius Zaleckas <paulius.zaleckas@gmail.com>,
Michal Suchanek <hramrach@centrum.cz>
Subject: Re: [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode
Date: Thu, 11 Mar 2010 10:12:52 -0500 [thread overview]
Message-ID: <a728f9f91003110712l407ed04dl28b86ef77a427218@mail.gmail.com> (raw)
In-Reply-To: <1268302426.7444.117.camel@thor.local>
2010/3/11 Michel Dänzer <michel@daenzer.net>:
> On Wed, 2010-03-10 at 13:10 -0500, Alex Deucher wrote:
>> On Wed, Mar 10, 2010 at 1:05 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
>> > On Wed, Mar 10, 2010 at 12:42 PM, James Simmons <jsimmons@infradead.org> wrote:
>> >>
>> >> See my other post about what fbdev really means in its historical
>> >> context. The struct fb_info really maps better to drm_crtc than to
>> >> drm_framebuffer. In fact take the case of the matrox fbdev driver. It
>> >> creates two framebuffer devices even tho it used one static framebuffer.
>> >> What the driver does is splits the framebuffer in two and assigned each
>> >> part to a CRTC.
>> >
>> > The only problem with that is that it eats a lot of memory for the
>> > console which limits X when it starts. On cards with limited vram ,
>> > you might not have enough memory left for any meaningful acceleration
>> > when X starts.
>>
>> It would be nice to find a way to reclaim the console memory for X,
>> but I'm not sure that can be done and still provide a good way to
>> provide oops support.
>
> What do you think the average user will care about more?
>
> * Seeing kernel oops/panic output about once in a lifetime.
> * Being able to start/use X in the first place and enabling it to
> use all of VRAM.
>
> Personally, I've never even seen any kernel oops/panic output despite
> numerous opportunities for that in the couple of months I've been using
> KMS. But I have spent considerable time and effort trying to get rid of
> the pinned fbcon BO. If the oops/panic output is the only thing
> preventing that, maybe that should only be enabled via some module
> option for developers.
I'm all for it!
Alex
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-03-11 15:12 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 13:16 [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Paulius Zaleckas
2009-11-20 15:55 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video Clemens Ladisch
2009-11-20 18:53 ` James Simmons
2009-11-20 19:05 ` Andrew Morton
2009-11-20 19:39 ` Paulius Zaleckas
2009-11-20 20:01 ` James Simmons
2009-11-20 20:13 ` Paulius Zaleckas
2009-11-20 20:48 ` James Simmons
2009-11-21 4:25 ` Dave Airlie
2009-11-21 4:27 ` Dave Airlie
2010-03-01 9:18 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Michal Suchanek
2010-03-03 5:02 ` Dave Airlie
2010-03-03 8:23 ` Michal Suchanek
2010-03-03 9:23 ` Dave Airlie
2010-03-03 10:32 ` Michal Suchanek
2010-03-10 18:11 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-10 21:04 ` Ville Syrjälä
2010-03-10 21:16 ` Michal Suchanek
2010-03-11 2:24 ` James Simmons
2010-03-11 2:22 ` James Simmons
2010-03-11 5:03 ` Ville Syrjälä
2010-03-10 18:04 ` James Simmons
2010-03-10 17:42 ` James Simmons
2010-03-10 18:05 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Alex Deucher
2010-03-10 18:10 ` Alex Deucher
2010-03-10 18:47 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-10 19:49 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Michal Suchanek
2010-03-10 20:06 ` Alex Deucher
2010-03-11 10:13 ` Michel Dänzer
2010-03-11 10:31 ` Pauli Nieminen
2010-03-11 15:12 ` Alex Deucher [this message]
2010-03-11 15:17 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-11 15:47 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Michal Suchanek
2010-03-12 14:52 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-12 20:51 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Dave Airlie
2010-03-13 14:40 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-13 21:01 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Dave Airlie
2010-03-14 11:41 ` Michel Dänzer
2010-03-15 18:38 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-16 13:46 ` Michel Dänzer
2010-03-16 13:56 ` James Simmons
2010-03-16 14:00 ` Michel Dänzer
2010-03-25 12:30 ` James Simmons
2010-03-15 18:22 ` James Simmons
2010-03-10 20:58 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Michal Suchanek
2010-03-11 3:41 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-10 17:35 ` James Simmons
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=a728f9f91003110712l407ed04dl28b86ef77a427218@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=hramrach@centrum.cz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=michel@daenzer.net \
--cc=paulius.zaleckas@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).