From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: "C Bergström" <cbergstrom@pathscale.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
Alex Williamson <alex.williamson@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Stupid NVIDIA 3D vgaarb.c patch
Date: Tue, 23 Sep 2014 18:25:09 +0200 [thread overview]
Message-ID: <20140923182509.46decd46@neptune.home> (raw)
In-Reply-To: <CA+55aFwX_nV9oUjh6u5WY=jpLxN-a5GFLmXQWDbHW0Yom9OOVA@mail.gmail.com>
On Mon, 22 September 2014 Linus Torvalds <torvalds@linux-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@pathscale.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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-09-23 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOnawYp7kv7Zjn4j-j4-TUOshE9G1uXWEqXB_=RHePNwNLmwWA@mail.gmail.com>
2014-09-22 20:43 ` Stupid NVIDIA 3D vgaarb.c patch Linus Torvalds
2014-09-22 20:52 ` C Bergström
2014-09-23 14:22 ` Peter Wu
2014-09-22 21:15 ` Alex Williamson
2014-09-22 21:20 ` C Bergström
2014-09-22 21:54 ` Alex Williamson
2014-09-22 22:10 ` Alex Deucher
2014-09-27 11:01 ` Pasi Kärkkäinen
2014-09-24 1:55 ` Alex Deucher
2014-09-23 16:25 ` Bruno Prémont [this message]
2014-09-23 20:29 ` Benjamin Herrenschmidt
2014-09-26 21:08 ` Aaron Plattner
2014-09-26 21:13 ` Ilia Mirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140923182509.46decd46@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=alex.williamson@redhat.com \
--cc=cbergstrom@pathscale.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).