From: Meelis Roos <mroos@linux.ee>
To: Dave Airlie <airlied@gmail.com>
Cc: 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: Mon, 9 Jul 2012 14:30:40 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1207090051120.3699@math.ut.ee> (raw)
In-Reply-To: <alpine.SOC.1.00.1207052224340.19147@math.ut.ee>
> > > In 3.4, radeon worked with a glitch - window titles were see-throug (not
> > > drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
> > > acceleration on this system at all. Full dmesg below.
> >
> > Does it always do it the same? got the dmesg from 3.4 and/or 2.6.32?
>
> That was a good question. I did some more tries, and it was not
> repeatable. Sometimes it worked like 3.4 did - rv100 initialized fine,
> no borders except when maximized, otherwise worked.
Re-tested 3.4.0-rc7 that I had availble from 3.4 times, it worked 4 out
of 4 times.
> Initial windows border problem seems to have been introduced between
> 2.6.37 and 2.6.38, bisect is slow.
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
get window titles) with radeon.modeset=0.
2.6.32 works and has kernel modesetting enabled from dmesg but I think I
did not notice screen going fbcon during boot... maybe it only used the
modesetting when X started.
So there are 2 different problems (maybe related), the new one above and
the old one of not seeing some window borders when modesetting and
acceleration are in use. Maximized windows do have borders.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2012-07-09 11:30 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 [this message]
2012-07-10 22:32 ` valdis.kletnieks
2012-07-11 10:43 ` Meelis Roos
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.1207090051120.3699@math.ut.ee \
--to=mroos@linux.ee \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.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
all inboxes | Powered by JetHome®