From: Eric Valette <eric.valette-GANU6spQydw@public.gmane.org>
To: Pekka Paalanen <pq-X3B1VOXEql0@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: When will nouveau kernel tree be merged into master
Date: Thu, 09 Jul 2009 21:51:23 +0200 [thread overview]
Message-ID: <4A564A3B.1050905@free.fr> (raw)
In-Reply-To: <20090709205154.4f613cc5-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
Pekka Paalanen wrote:
> Sorry for causing that much trouble.
>
> On Thu, 09 Jul 2009 19:20:54 +0200
> Eric Valette <eric.valette-GANU6spQydw@public.gmane.org> wrote:
>
>> Well I would suggest you to look at GALLIUM3D because using gi to clone
>> mesa master is not even working and even if you get a git snapshot it
>> does not build.
>
> http://nouveau.freedesktop.org/wiki/GalliumHowto
> Is there something unclear here?
The command
git clone git://anongit.freedesktop.org/git/mesa/mesa
Does not work for me while others do. It hangs indefinitely (I let it
run once half a day, doing strace to see that I was waiting to a read on
a socket).
> Also, I'd recommend studying git, you only ever have to 'clone' once.
If the full clone requires a day on 1Mbit sped, I guess you will have
few volunteers.
> Receiving updates is a lot faster.
I tool you in the first mail, I use drm git, xf86-video-nouveau git and
you still suggest I should learn how to use git? In my kernel udate
script I have git fetch ; git rebase origin for several trees. I ommited
mesa because of the bug
> InstallDRM has the instructions, since
> the kernel tree is so big, but there are more than one way to pull updates.
I do not mind you use a whole kernel tree provide you provide automated
way to extract diff compared to the kernel you pull in. I've found the
tarball already but will rather extract the whole code and modify my
rather complex kernel update script to move original drm directory back
and forth for the sake of using still using ketchup, drm git update
xf86-video-nouveau git update and regular kernel patching way.
-- eric
next prev parent reply other threads:[~2009-07-09 19:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 12:00 When will nouveau kernel tree be merged into master Eric Valette
[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 ` 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 [this message]
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=4A564A3B.1050905@free.fr \
--to=eric.valette-ganu6spqydw@public.gmane.org \
--cc=dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=pq-X3B1VOXEql0@public.gmane.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.