Displaying 4 results from an estimated 4 matches for "bootfp".
Did you mean:
bootfs
2013 Oct 02
2
Resource map sanity check fails after GRUB "keeps" the gfx mode
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
2013 Oct 03
2
Resource map sanity check fails after GRUB "keeps" the gfx mode
...fine. It's the
default and is what pre-3.12 kernels always did.
> I tried four combinations: with and without IORESOURCE_BUSY and with
> and without the PCI resource adjustment. The only combination when
> nvidiafb probes the hardware is when IORESOURCE_BUSY is not used and
> the BOOTFP resource is adjusted to match the PCI BAR.
A dmesg log would be nice, but I assume nvidiafb fails because it
cannot map its BAR regions?
> It means that your patch by itself won't prevent nvidiafb from getting
> the resource on my hardware (ThinkPad W530). However, if the BOOTFP
> r...
2013 Oct 03
0
Resource map sanity check fails after GRUB "keeps" the gfx mode
...n 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. The only combination when
nvidiafb probes the hardware is when IORESOURCE_BUSY is not used and
the BOOTFP resource is adjusted to match the PCI BAR.
It means that your patch by itself won't prevent nvidiafb from getting
the resource on my hardware (ThinkPad W530). However, if the BOOTFP
resource matches the PCI BAR for the video card, adding IORESOURCE_BUSY
might prevent some framebuffer drivers...
2013 Oct 04
0
Resource map sanity check fails after GRUB "keeps" the gfx mode
...id.
Of course, you are right, I missed sysfb.h.
> > I tried four combinations: with and without IORESOURCE_BUSY and with
> > and without the PCI resource adjustment. The only combination when
> > nvidiafb probes the hardware is when IORESOURCE_BUSY is not used and
> > the BOOTFP resource is adjusted to match the PCI BAR.
>
> A dmesg log would be nice, but I assume nvidiafb fails because it
> cannot map its BAR regions?
The logs are adjusted and so it the kernel config file.
$ grep nvidiafb *
dm-busy-adjust:nvidiafb_setup START
dm-busy-adjust:nvidiafb_probe STAR...