From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Date: Thu, 19 Dec 2013 12:31:37 +0000 Subject: Re: cirrusdrmfb broken with simplefb Message-Id: <20131219123137.GC18110@gmail.com> List-Id: References: <20131218092941.GA19210@gmail.com> <20131219000346.0f722b65@alan.etchedpixels.co.uk> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: David Herrmann Cc: One Thousand Gnomes , linux-kernel , Takashi Iwai , Stephen Warren , "linux-fbdev@vger.kernel.org" , the arch/x86 maintainers * David Herrmann wrote: > Hi > > On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes > wrote: > >> > That bug always existed, simplefb is just the first driver to hit it > >> > (vesafb/efifb didn't use resources). I'm aware of the issue but as a > >> > workaround you can simply disable CONFIG_X86_SYSFB. That restores > >> > the old behavior. > >> > >> This looks like a regression, so we'll either need a fix or we'll have > >> to mark CONFIG_X86_SYSFB as CONFIG_BROKEN. > > > > Kernel bugzilla has entries for simplefb breaking both vesafb and > > matrox mga. > > Thanks for the hints. I've read through all I could find and tried > to provide some help. > > I'm kind of confused, most of them enable CONFIG_X86_SYSFB (which is > 'n' by default) but don't read the help text. I did my best to tell > people that this option requires CONFIG_FB_SIMPLE, but if you don't > read the help-text you won't notice that. Don't know what to do > about that.. People generally don't read the help text - still the kernel should not break. So please the Kconfig angle (and the bootup logic, etc.) fool-proof, graphics failures are not fun to debug! Thanks, Ingo