lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140923182509.46decd46@neptune.home>
Date:	Tue, 23 Sep 2014 18:25:09 +0200
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	C Bergström <cbergstrom@...hscale.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	dri-devel@...ts.freedesktop.org, David Airlie <airlied@...ux.ie>,
	Alex Williamson <alex.williamson@...hat.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Stupid NVIDIA 3D vgaarb.c patch

On Mon, 22 September 2014 Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> Adding proper people and mailing lists..
> 
> The PCI_CLASS_DISPLAY_VGA test goes back to the very beginning by
> BenH, and I have no idea if adding PCI_CLASS_DISPLAY_3D is
> appropriate, but hopefully somebody does. The fact that it makes
> things work certainly argues fairly convincingly for it, but I want
> some backup here.
> 
> Dave, BenH?
> 
> Christopher(?), can you please also specify which laptop etc. And the
> patch itself seems to have come from somebody else, unless you're
> Lekensteyn. So we'd want to get the provenance of that too.

More a question to Christopher, but what criteria is preventing the use
of the NVIDIA GPU under this condition?

As far as I've seen on my (single-GPU) systems X requires the GPU to
have boot_vga=1 sysfs attribute to accept autoconfiguration (though
with two GPUs and optimus/switcheroo interaction between the GPUs may
change the picture).

I've been looking at the open, nouveau side of things only. If NVIDIA
closed driver has some other requirement, I don't know.

But as here the intention seems to be to use exclusively the NVIDIA GPU
just leaving the IGD along it should require explicit X configuration
which then does not care about boot_vga.


A more detailed description of what prevents operation with GPU not
being added to vgaarb would certainly help understanding what happens,
what is expected and where things differ.

Bruno

>                 Linus
> 
> On Mon, Sep 22, 2014 at 1:28 PM, C Bergström <cbergstrom@...hscale.com> wrote:
> > Hi Linus,
> >
> > I don't know who the original author is and I can have one of the distro
> > graphics friends review it, but I need this patch below to get NVIDIA
> > drivers to work (without using any Intel graphics) on my laptop
> > http://pastebin.com/wpmFi38k
> >
> > Sorry - I know this is not the proper way to submit a patch, but it's
> > trivial and I'm not a kernel dev.
> >
> > Thanks
> >
> > ./C
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ