On 11 March 2010 16:17, James Simmons <jsimm...@infradead.org> wrote: > >> >> 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! > > I'm looking into the details for this. It will require some changes to > internal apis to make it to work. >
Can't it print the oops on whatever is currently displayed? It need not be a dedicated buffer as long as there is always some buffer. But perhaps this is more complex than that. Thanks Michal ------------------------------------------------------------------------------ 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 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
