From: Eric Valette <Eric.Valette@Free.fr>
To: nouveau@lists.freedesktop.org
Cc: dri-devel@lists.sourceforge.net
Subject: When will nouveau kernel tree be merged into master
Date: Thu, 09 Jul 2009 14:00:29 +0200 [thread overview]
Message-ID: <4A55DBDD.6030703@Free.fr> (raw)
Hi,
I've been using nouveau driveau for 8 months or so, using automated
build from drm git, xf86-video-nouveau git and even sometimes mesa drm
git and discovered the linux-core build did not build the nouveau
driver the hard way: X was refusing to start as the nouveau.ko modules
was not loaded nor build. Build process did chnage without obvious way
to know womething was wrong.
Then I tried to build it by hand as the nouveau directory is still there
but compilation fails! I wonder why the code is still in the tree as it
make me waste quite some time trying to find where the missing
definitions had gone.
After some hours of goggling I discovered there was an git kernel tree
for nouveau. Got the feeling from dri-devel posts it was supposed to be
merged for rc1, checked master tree and found it was not merged.
So my question are:
- Why not purely delete nouveau files from linux-core and issue
error messages?
- When will nouveau in kernel git tree be merged? I know the merge
windows is closed but that usually does not hold for new drivers
Thanks. Using nouveau is quite painfull. Please be aware that as
distribution move too slowly into nominal nouveau driver support, I'm
not probably the only guy lost in the dust.
-- eric
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
--
next reply other threads:[~2009-07-09 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 12:00 Eric Valette [this message]
[not found] ` <6d4bc9fc0907090806h6b0f7de3i9f7ec673e2cc0e7d@mail.gmail.com>
[not found] ` <4A560B8C.7070809@Free.fr>
[not found] ` <4A560B8C.7070809-rC/V9kRXU7Q@public.gmane.org>
2009-07-09 15:31 ` When will nouveau kernel tree be merged into master Maarten Maathuis
[not found] ` <6d4bc9fc0907090831n64ca31d1pf6d025ef290b3614-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-09 16:38 ` Pekka Paalanen
[not found] ` <20090709193853.3dcff28c-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2009-07-09 17:24 ` Eric Valette
[not found] ` <4A5627BF.10807-GANU6spQydw@public.gmane.org>
2009-07-09 17:46 ` Maarten Maathuis
[not found] ` <4A55DBDD.6030703-rC/V9kRXU7Q@public.gmane.org>
2009-07-09 16:30 ` Pekka Paalanen
[not found] ` <20090709193053.5a5d6430-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2009-07-09 17:20 ` Eric Valette
[not found] ` <4A5626F6.4090607-GANU6spQydw@public.gmane.org>
2009-07-09 17:51 ` Pekka Paalanen
[not found] ` <20090709205154.4f613cc5-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2009-07-09 19:51 ` Eric Valette
2009-07-10 7:39 ` [Nouveau] " Sean Estabrooks
[not found] ` <BLU0-SMTP5459C57EAE328F89E4E6B5AE270-MsuGFMq8XAE@public.gmane.org>
2009-07-10 8:10 ` Eric Valette
[not found] ` <4A56F779.2090303-rC/V9kRXU7Q@public.gmane.org>
2009-07-10 17:40 ` Eric Valette
2009-07-10 9:18 ` Eric Valette
2009-07-10 17:46 ` Eric Valette
[not found] ` <4A564A3B.1050905-GANU6spQydw@public.gmane.org>
2009-07-10 9:22 ` Michel Dänzer
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=4A55DBDD.6030703@Free.fr \
--to=eric.valette@free.fr \
--cc=dri-devel@lists.sourceforge.net \
--cc=nouveau@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.