From: Clemens Schwaighofer <cs@tequila.co.jp>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Radeon FB slightly broken in 2.6.8.x
Date: Mon, 16 Aug 2004 19:56:08 +0900 [thread overview]
Message-ID: <412092C8.1050102@tequila.co.jp> (raw)
In-Reply-To: <1092622048.9529.38.camel@gaston>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Benjamin Herrenschmidt wrote:
|
| Does it disappear if you use video=radeonfb:noaccel on the kernel
| command line ?
fb works fine with noccel given.
lg, clemens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBIJLIjBz/yQjBxz8RAtZfAKCYGdb/AjheuVtrwTZ5QhnTiRJinQCfXvJd
pZ+ilA1VPpzdb4FURDP1EJg=
=FeHS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-08-16 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 13:05 Radeon FB slightly broken in 2.6.8.x Clemens Schwaighofer
2004-08-15 22:29 ` Benjamin Herrenschmidt
2004-08-16 0:13 ` Clemens Schwaighofer
2004-08-16 2:07 ` Benjamin Herrenschmidt
2004-08-16 3:05 ` Clemens Schwaighofer
2004-08-16 10:56 ` Clemens Schwaighofer [this message]
2004-08-17 3:44 ` Benjamin Herrenschmidt
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=412092C8.1050102@tequila.co.jp \
--to=cs@tequila.co.jp \
--cc=benh@kernel.crashing.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