From: Meelis Roos <mroos@linux.ee>
To: valdis.kletnieks@vt.edu
Cc: Dave Airlie <airlied@gmail.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: 3.5-rc5: radeon acceleration regression on Transmeta system
Date: Wed, 11 Jul 2012 13:43:55 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1207111340360.12880@math.ut.ee> (raw)
In-Reply-To: <60495.1341959530@turing-police.cc.vt.edu>
> > It's actually more complicated than that. Old kernel images started
> > misbehaving from around 2.6.35-rc5 and any kernel older than that was
> > OK. When I recompiled the older kernels with squeeze gcc (migh have been
> > lenny gcc before, or different answers to make oldconfig), anything from
> > current git down to 2.6.33 is broken with radeon.modeset=1 and works (I
>
> What releases of GCC were those? I'm chasing an issue where compiling
> with 4.7.[01] breaks but 4.6.2 is OK, wondering if we're chasing the same thing.
I do not remember when I upgraded from lenny to squeeze. It the previous
gcc was lenny's, it was gcc version 4.3.2 (Debian 4.3.2-1.1). The gcc in
current stable (squeeze) is gcc version 4.4.5 (Debian 4.4.5-8). Since
the old laptop is somewhat slow for following unstable, I have not tried
any newer gcc version on that machine, and it has been compiling its own
kernels for stress-testing purposes.
So it's probably not related to gcc 4.6->4.7 changes.
--
Meelis Roos (mroos@linux.ee)
prev parent reply other threads:[~2012-07-11 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 7:00 Meelis Roos
2012-07-05 7:03 ` Dave Airlie
2012-07-05 19:40 ` Meelis Roos
2012-07-09 11:30 ` Meelis Roos
2012-07-10 22:32 ` valdis.kletnieks
2012-07-11 10:43 ` Meelis Roos [this message]
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=alpine.SOC.1.00.1207111340360.12880@math.ut.ee \
--to=mroos@linux.ee \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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
all inboxes | Powered by JetHome®