public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Stephane Marchesin <stephane.marchesin@gmail.com>,
	Maarten Maathuis <madman2003@gmail.com>,
	Xavier Bestel <xavier.bestel@free.fr>,
	Dave Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sf.net
Subject: Re: [git pull] drm
Date: Fri, 11 Dec 2009 12:49:34 -0500	[thread overview]
Message-ID: <4B22862E.5050407@garzik.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0912110710510.3560@localhost.localdomain>

On 12/11/2009 10:28 AM, Linus Torvalds wrote:
>
>
> On Fri, 11 Dec 2009, Jeff Garzik wrote:
>>
>> F11 uses nouveau here.  It is actually a pain to get 'nv' going as an
>> alternate -- bugs have been filed.  Makes kernel dev more difficult for me.  I
>> was actually told, by Fedora people, that I should be hacking on the Fedora
>> (rpm-based) kernel, rather than a 100% upstream kernel like I have been
>> hacking/booting for the past decade, as a result of this setup (needing
>> nouveau kernel support, thus needing Fedora rather than upstream kernel).
>
> Btw, for all my ranting (and maybe Alan is right, and I'm ranting at the
> wrong people - it's just that the actual driver authors aren't the ones
> that violated any rules), I do have to give kudos for the fact that the
> F12 situation seems to be much better.
>
> These days, what you can do is basically do all development (assuming it's
> not nouveau development) in the upstream kernel, and then you just have a
> separate 'nouveau' git tree (or branch) that you pull in the nouvea stuff
> into.
>
> That tree/branch will be a mess of random merges-of-the-day, but you'll
> never push it out to anybody anyway, so nobody cares. And building that
> messy merge tree will get you a working setup without any extra steps - a
> simple "make modules_install ; make install" will JustWork(tm).

At the outset, I was hoping for an even more straightforward solution: 
"if nouveau kernel mod not present, fall back to nv"  That would work 
without any kernel modifications at all.

But the answer came back as "if you run Fedora, run a Fedora kernel, 
otherwise don't expect anything to work"  My experience directly 
contradicts claims of "upstream first" policy, both in code and attitude.

I am looking into doing the git tree merge you suggest right now....  I 
didn't know that was an option, given ongoing API changes.  That would 
make my life quite a bit easier.  As you note, anything graphics is 
_glacially_ slow due to vesa fallback, when using a 100% upstream kernel.

	Jeff



  reply	other threads:[~2009-12-11 17:49 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10  6:17 [git pull] drm Dave Airlie
2009-12-10 15:17 ` Linus Torvalds
2009-12-10 15:40   ` Xavier Bestel
2009-12-10 16:24     ` Linus Torvalds
2009-12-10 17:40       ` Maarten Maathuis
2009-12-10 18:42         ` Linus Torvalds
2009-12-10 19:13           ` Pekka Enberg
2009-12-10 19:13           ` Robert Noland
2009-12-10 19:28           ` Alan Cox
2009-12-10 19:36           ` Jesse Barnes
2009-12-10 19:37           ` Dave Airlie
2009-12-10 19:45             ` Roland Dreier
2009-12-10 19:49           ` Pekka Paalanen
2009-12-10 20:35             ` Will Dyson
2009-12-10 21:12               ` Pekka Paalanen
2009-12-10 19:53           ` Stephane Marchesin
2009-12-10 23:37             ` Linus Torvalds
2009-12-10 23:50               ` Dave Airlie
2009-12-10 23:58               ` Alan Cox
2009-12-11  0:09                 ` Linus Torvalds
2009-12-11  0:20                   ` "C. Bergström"
2009-12-11  0:32                     ` Linus Torvalds
2009-12-11  0:47                       ` Dave Airlie
2009-12-11  1:34                       ` Kyle McMartin
2009-12-11  0:21                   ` Dave Airlie
2009-12-11  0:45                     ` Linus Torvalds
2009-12-11  9:18                   ` Alan Cox
2009-12-11  9:34                     ` David Miller
2009-12-11 10:15                       ` Andy Walls
2009-12-11 10:20                       ` Dave Airlie
2009-12-11 12:45                         ` tytso
2009-12-11 12:50                           ` Alan Cox
2009-12-11 10:28                     ` Jeff Garzik
2009-12-11 10:46                       ` Dave Airlie
2009-12-11 15:28                       ` Linus Torvalds
2009-12-11 17:49                         ` Jeff Garzik [this message]
2009-12-11 10:02                 ` Stephane Marchesin
2009-12-11 10:24                   ` Andy Walls
2009-12-10 16:47     ` Alan Cox
2009-12-10 21:49       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2011-02-04  5:11 Dave Airlie
2010-02-11  4:20 Dave Airlie
2010-02-15  9:53 ` Christian Borntraeger
2010-02-15 20:12   ` Marcin Slusarz
2010-02-15 20:39     ` Maarten Maathuis
2010-02-15 22:13       ` Marcin Slusarz
2010-02-15 22:55   ` Christian Borntraeger
2010-02-16  1:19     ` Ben Skeggs
2010-02-16 11:39       ` Christian Borntraeger
2010-01-11  4:52 Dave Airlie
2009-09-29  3:52 Dave Airlie
2009-09-29  4:26 ` [git pull] drm Dave Airlie
2009-02-09  8:30 Dave Airlie
2009-01-07  1:59 Dave Airlie
2008-12-29  8:32 Dave Airlie
2009-01-04 19:19 ` Gabriel C
2009-01-10  2:03   ` Dave Airlie
2009-01-09 15:07 ` Richard Purdie
2009-01-09 18:03   ` Richard Purdie
2009-01-10  1:13     ` Richard Purdie
2009-01-10  2:04       ` Dave Airlie
2009-01-10  9:58         ` Richard Purdie
2009-01-10 23:04           ` Dave Airlie
2009-01-10 23:51             ` Richard Purdie
2009-01-16  6:53               ` Brice Goglin
2009-01-11  9:29   ` Graham Murray
2009-01-11  9:56     ` Dave Airlie

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=4B22862E.5050407@garzik.org \
    --to=jeff@garzik.org \
    --cc=airlied@linux.ie \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dri-devel@lists.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madman2003@gmail.com \
    --cc=stephane.marchesin@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xavier.bestel@free.fr \
    /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