From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, "Pfiffer,
AndrewX K" <andrewx.k.pfiffer@intel.com>,
sylvain.meyer@worldonline.fr
Subject: Re: PATCH: fbdev: intelfb - workaround for 830M
Date: Thu, 13 Jan 2005 21:05:42 +0800 [thread overview]
Message-ID: <200501132105.42219.adaplas@hotpop.com> (raw)
In-Reply-To: <69F69FD5FD4A9843ACBF7CE9B7830B4A02DCA461@orsmsx408>
On Friday 07 January 2005 09:00, Pfiffer, AndrewX K wrote:
> This is a work around for the 830M with intelfb. Relative to 2.6.10.
> Without this patch, updates to the DSPACNTR register will be ignored.
Can you resend? Patch is line-wrapped.
Tony
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
prev parent reply other threads:[~2005-01-13 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 1:00 PATCH: fbdev: intelfb - workaround for 830M Pfiffer, AndrewX K
2005-01-13 13:05 ` Antonino A. Daplas [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=200501132105.42219.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=andrewx.k.pfiffer@intel.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sylvain.meyer@worldonline.fr \
/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).