dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Paweł Sikora" <pawel.sikora@agmk.net>
To: Heinz Diehl <htd@fritha.org>
Cc: Martin Peres <martin.peres@labri.fr>,
	Heinz Diehl <htd@fancy-poultry.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	David Airlie <airlied@linux.ie>, Ben Skeggs <bskeggs@redhat.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	marcheu@chromium.org, Marcin Slusarz <marcin.slusarz@gmail.com>,
	Lekensteyn <lekensteyn@gmail.com>
Subject: Re: Linux 3.7-rc1 (nouveau_bios_score oops).
Date: Fri, 26 Oct 2012 21:51:37 +0200	[thread overview]
Message-ID: <4392132.ui6koSANok@localhost> (raw)
In-Reply-To: <20121025180654.GA28920@fritha.org>

On Thursday 25 of October 2012 20:06:54 Heinz Diehl wrote:
> On 25.10.2012, Paweł Sikora wrote: 
> 
> > what is the reason of loading nouveau driver for laptops 
> > with nvidia optimus and enabling vga switcheroo
> > which doesn't work in such (optimus) cases.
> 
> You can safely compile a kernel without nouveau, your Nvidia 
> card will not be used at all since neither Linux nor the 
> proprietary nvidia driver does support optimus at this time
> (and frankly, I won't buy any further machines with opticrap).
> So having nouveau compiled and loaded seems like a waste of ressources
> in this case.

i've bought this asus laptop mostly for a developer's workstation replacement
(quad-core-i7-avx cpu with integrated gpu, with 12GB ram and 2x500GB hdd).
nvidia's addon is an optional crap :)

> For me it's important to have nouveau working, because I try/use
> Bumblebee and optirun: 
> 
> http://bumblebee-project.org/
> https://fedoraproject.org/wiki/Bumblebee

i'll try to use transformers too :-)

      reply	other threads:[~2012-10-26 19:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1724445.dN2yMEzN6d@localhost>
2012-10-19 21:25 ` Linux 3.7-rc1 (nouveau_bios_score oops) Linus Torvalds
2012-10-19 22:41   ` Martin Peres
2012-10-19 22:52     ` Linus Torvalds
2012-10-20  9:26   ` Heinz Diehl
2012-10-20  9:40     ` Martin Peres
2012-10-20 10:42       ` Heinz Diehl
2012-10-20 20:28         ` Marcin Slusarz
2012-10-20 20:35           ` Marcin Slusarz
2012-10-20 21:20           ` Heinz Diehl
2012-10-20 21:42             ` Marcin Slusarz
2012-10-20 21:45               ` Marcin Slusarz
2012-10-21  8:54               ` Heinz Diehl
2012-10-20 22:19             ` Marcin Slusarz
2012-10-21  6:58               ` Paweł Sikora
2012-10-21  9:26                 ` Heinz Diehl
2012-10-21 12:09                 ` Marcin Slusarz
2012-10-21 13:31                   ` Heinz Diehl
2012-10-21 14:38                   ` Linus Torvalds
2012-10-21 14:49                     ` Marcin Slusarz
2012-10-21 17:13                       ` Linus Torvalds
2012-10-21 20:07                       ` Lekensteyn
2012-10-22  0:07               ` Ben Skeggs
2012-10-25 17:53       ` Paweł Sikora
2012-10-25 18:06         ` Heinz Diehl
2012-10-26 19:51           ` Paweł Sikora [this message]

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=4392132.ui6koSANok@localhost \
    --to=pawel.sikora@agmk.net \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=htd@fancy-poultry.org \
    --cc=htd@fritha.org \
    --cc=lekensteyn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcheu@chromium.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=martin.peres@labri.fr \
    --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).