From: Ed Tomlinson <tomlins@cam.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Dave Airlie <airlied@gmail.com>
Subject: Re: 2.6.13-rc3-mm2/mm1 breaks DRI
Date: Wed, 27 Jul 2005 17:58:52 -0400 [thread overview]
Message-ID: <200507271758.52466.tomlins@cam.org> (raw)
In-Reply-To: <20050727024330.78ee32c2.akpm@osdl.org>
>> >>
>> >> I also use 2.6.13-rc3-mm1. Will try with a previous version an report to lkml if
>> >> it works.
>> >>
>> >
>> > I just tried 13-rc2-mm1 and dri is working again. Its reported to also work
>> > with 13-rc3.
>>
>
>Hmm no idea what could have broken it, I'm at OLS and don't have any
>DRI capable machine here yet.. so it'll be a while before I get to
>take a look at it .. I wouldn't be terribly surprised if some of the
>new mapping code might have some issues..
Still happens with mm2.
Thanks
Ed
next prev parent reply other threads:[~2005-07-27 22:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 9:43 2.6.13-rc3-mm2 Andrew Morton
2005-07-27 10:08 ` 2.6.13-rc3-mm2 Sam Ravnborg
2005-07-27 10:14 ` 2.6.13-rc3-mm2 Andrew Morton
2005-07-27 12:08 ` 2.6.13-rc3-mm2 (kbuild broken for external modules) Miklos Szeredi
2005-07-27 12:31 ` Brice Goglin
2005-07-27 19:16 ` Sam Ravnborg
2005-07-28 11:11 ` Miklos Szeredi
2005-07-27 20:35 ` 2.6.13-rc3-mm2 doesn't boot Adrian Bunk
2005-07-27 21:16 ` Andrew Morton
2005-07-27 22:20 ` Adrian Bunk
2005-07-27 20:48 ` 2.6.13-rc3-mm2 Andrew James Wade
2005-07-27 21:11 ` 2.6.13-rc3-mm2 Andrew Morton
2005-07-27 21:27 ` 2.6.13-rc3-mm2 David S. Miller
2005-07-27 21:58 ` Ed Tomlinson [this message]
2005-07-29 0:37 ` 2.6.13-rc3-mm2/mm1 breaks DRI Ed Tomlinson
2005-07-29 0:41 ` Dave Airlie
2005-07-29 10:52 ` Ed Tomlinson
2005-07-30 4:03 ` Dave Airlie
2005-08-17 12:33 ` Dave Airlie
2005-07-28 10:06 ` 2.6.13-rc3-mm2 Borislav Petkov
2005-07-28 15:01 ` 2.6.13-rc3-mm2 Martin J. Bligh
2005-07-28 17:41 ` 2.6.13-rc3-mm2 Andrew Morton
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=200507271758.52466.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=airlied@gmail.com \
--cc=akpm@osdl.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