From: Jeff Hartmann <jhartmann@valinux.com>
To: Gareth Hughes <gareth.hughes@acm.org>
Cc: DRI-Devel <dri-devel@lists.sourceforge.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [Dri-devel] Re: DRM Linux kernel merge (update) needed, soon.
Date: Wed, 08 Aug 2001 10:44:55 -0600 [thread overview]
Message-ID: <3B716C87.7010907@valinux.com> (raw)
In-Reply-To: <20010807014029Z270029-28344+2126@vger.kernel.org> <3B6F86BA.14D449F4@acm.org>
Gareth Hughes wrote:
> Dieter Nützel wrote:
>
>> the Linux kernel DRM stuff need a merge (update), soon.
>> Even the (latest) 2.4.7-ac (3-8) stuff has some cleanups but didn't work with
>> the tdfx DRI CVS trunk driver for example.
>> I have to build the DRI CVS tdfx.o kernel module to get it working, again.
>> If I read it right the kernel stuff include some needed fixes...
>
>
> Agreed.
>
> After being let go from VA, I've had to return all the graphics cards
> and machines they loaned me, and as my own supply of cards (and indeed
> all of my computer gear) is in storage somewhere in the US there isn't
> much I can do about fixing this. You'll have to pester the guys at VA,
> most likely Jeff Hartmann.
>
> Jeff?
>
> -- Gareth
>
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/dri-devel
>
I sent a patch to Linus and Alan this morning.
-Jeff
next prev parent reply other threads:[~2001-08-08 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 1:40 DRM Linux kernel merge (update) needed, soon Dieter Nützel
2001-08-07 6:12 ` Gareth Hughes
2001-08-08 16:44 ` Jeff Hartmann [this message]
2001-08-09 6:04 ` [Dri-devel] " Keith Owens
2001-08-07 14:35 ` Alan Cox
2001-08-07 15:05 ` Dieter Nützel
[not found] <no.id>
2001-08-08 16:53 ` [Dri-devel] " Alan Cox
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=3B716C87.7010907@valinux.com \
--to=jhartmann@valinux.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=gareth.hughes@acm.org \
--cc=linux-kernel@vger.kernel.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