From: Nicholas Wourms <dragon@gentoo.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: jsimmons@infradead.org
Subject: Re: [BK UPDATES] Frmaebuffer updates.
Date: Sun, 23 Mar 2003 08:05:49 -0500 [thread overview]
Message-ID: <3E7DB12D.3080006@gentoo.org> (raw)
In-Reply-To: Pine.LNX.4.44.0303230314210.30614-100000@phoenix.infradead.org
James Simmons wrote:
> Linus, please do a
>
> bk pull http://fbdev.bkbits.net/fbdev-2.5
>
> This is the bulk of the framebuffer changes. It has many important fixes
> that are needed. Please apply. Normal diff is avaliable at
>
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
>
> Thank you.
>
> This will update the following files:
[SNIP]
James,
This change just broke the updated fix for matroxfb that
Petr provided. So, with all due respect, where do you (or
anyone else) stand on getting matroxfb working again? I'm
not complaining, but matrox cards are *supposed* to be the
most supported cards by linux, which was one of the factors
which led me to buy one. I know nothing about video
programming, otherwise I'd try doing it myself. Thanks for
all the hardwork you and others have done so far.
Cheers,
Nicholas
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
prev parent reply other threads:[~2003-03-23 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 3:16 [BK UPDATES] Frmaebuffer updates James Simmons
2003-03-23 13:05 ` Nicholas Wourms [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=3E7DB12D.3080006@gentoo.org \
--to=dragon@gentoo.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.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).