search for: create_simplefb

...nce. nvidiafb cannot access the >> > resources if IORESOURCE_BUSY is used. >> >> Are you sure this is related to IORESOURCE_BUSY? Or is it related to >> CONFIG_X86_SYSFB? > > CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would > compile without it. create_simplefb() is used in > arch/x86/kernel/sysfb.c that is compiled unconditionally and that > function is defined in arch/x86/kernel/sysfb_simplefb.c that is only > compiled if CONFIG_X86_SYSFB is defined. You can set CONFIG_X86_SYSFB=n and everything works fine. It's the default and is what pre...

Hi Pavel On Wed, Oct 2, 2013 at 11:46 PM, Pavel Roskin <proski at gnu.org> wrote: > On Wed, 2 Oct 2013 16:47:29 +0200 > David Herrmann <dh.herrmann at gmail.com> wrote: > >> Thanks for your investigations. I finally sent my patch and put you on >> CC. Sorry for the delay, but I have mostly catched up with all emails >> now. >> >> This really just

...kernel/sysfb_simplefb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kernel/sysfb_simplefb.c b/arch/x86/kernel/sysfb_simplefb.c index 22513e9..b7bb615 100644 --- a/arch/x86/kernel/sysfb_simplefb.c +++ b/arch/x86/kernel/sysfb_simplefb.c @@ -79,7 +79,7 @@ __init int create_simplefb(const struct screen_info *si, /* setup IORESOURCE_MEM as framebuffer memory */ memset(&res, 0, sizeof(res)); - res.flags = IORESOURCE_MEM; + res.flags = IORESOURCE_MEM | IORESOURCE_BUSY; res.name = simplefb_resname; res.start = si->lfb_base; res.end = si->lfb_base + len - 1;...

...owever, there is some difference. nvidiafb cannot access the > > resources if IORESOURCE_BUSY is used. > > Are you sure this is related to IORESOURCE_BUSY? Or is it related to > CONFIG_X86_SYSFB? CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would compile without it. create_simplefb() is used in arch/x86/kernel/sysfb.c that is compiled unconditionally and that function is defined in arch/x86/kernel/sysfb_simplefb.c that is only compiled if CONFIG_X86_SYSFB is defined. I tried four combinations: with and without IORESOURCE_BUSY and with and without the PCI resource adjustment....

On Fri, 4 Oct 2013 01:08:34 +0200 David Herrmann <dh.herrmann at gmail.com> wrote: > > CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would > > compile without it. create_simplefb() is used in > > arch/x86/kernel/sysfb.c that is compiled unconditionally and that > > function is defined in arch/x86/kernel/sysfb_simplefb.c that is only > > compiled if CONFIG_X86_SYSFB is defined. > > You can set CONFIG_X86_SYSFB=n and everything works fine. It's th...

Hello! I'm getting this backtrace every time I boot: resource map sanity check conflict: 0xf0000000 0xf1ffffff 0xf1000000 0xf112bfff BOOTFB ------------[ cut here ]------------ WARNING: CPU: 6 PID: 1 at /home/proskin/src/linux/arch/x86/mm/ioremap.c:171 __ioremap_caller+0x372/0x380() Info: mapping multiple BARs. Your kernel is fine. Modules linked in: CPU: 6 PID: 1 Comm: swapper/0 Not tainted