From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Miles Lane <miles@megapathdsl.net>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
James Simmons <jsimmons@transvirtual.com>
Subject: Re: Rivafb not working properly in kernel 2.5.15.
Date: Sat, 11 May 2002 11:50:43 -0400 [thread overview]
Message-ID: <3CDD3DD3.2060600@mandrakesoft.com> (raw)
In-Reply-To: 3CDD34E4.4040803@megapathdsl.net
Miles Lane wrote:
> I am running development kernel 2.5.15 and am having some
> trouble getting rivafb to display in the correct mode.
Does 2.4.19-pre8 work for you?
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
next prev parent reply other threads:[~2002-05-11 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-11 15:12 Rivafb not working properly in kernel 2.5.15 Miles Lane
2002-05-11 15:50 ` Jeff Garzik [this message]
2002-05-12 8:02 ` Miles Lane
2002-05-12 17:34 ` Ani Joshi
2002-05-12 18:26 ` Miles Lane
2002-05-13 0:51 ` Miles Lane
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=3CDD3DD3.2060600@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=miles@megapathdsl.net \
/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).