From: Henrik Christian Grove <grove@sslug.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: Radeon framebuffer problems i 2.6.0-test6
Date: 30 Sep 2003 23:03:45 +0200 [thread overview]
Message-ID: <7gd6di0z0u.fsf@serena.fsr.ku.dk> (raw)
In-Reply-To: <Bz8D.La.11@gated-at.bofh.it>
Henrik Christian Grove <grove@sslug.dk> writes:
> Searching through the archives I have found some reports of problems
> with the radeon framebuffer, but done that seems to fully match my
> experiences.
So I forgor the question: Am I doing something totally wrong? Is there
something I can do to make the Radeon framebuffer work?
.Henrik
--
... applications which need to address vast amounts of memory
(e.g., big scientific crankers, large databases, emacs) ...
-- fra en artikel i LWN
next parent reply other threads:[~2003-09-30 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Bz8D.La.11@gated-at.bofh.it>
2003-09-30 21:03 ` Henrik Christian Grove [this message]
2003-09-30 20:12 Radeon framebuffer problems i 2.6.0-test6 Henrik Christian Grove
2003-09-30 22:05 ` Peter Osterlund
2003-09-30 23:31 ` Peter Chubb
2003-10-01 8:03 ` Pontus Fuchs
2003-10-01 9:02 ` Henrik Christian Grove
2003-10-01 22:20 ` Ani Joshi
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=7gd6di0z0u.fsf@serena.fsr.ku.dk \
--to=grove@sslug.dk \
--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;
as well as URLs for NNTP newsgroup(s).