From: "Thomas Backlund" <tmb@iki.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4.21-rc6-ac1] vesafb fixes...
Date: Mon, 2 Jun 2003 16:40:02 +0300 [thread overview]
Message-ID: <bbfjv8$gpe$1@main.gmane.org> (raw)
In-Reply-To: 200306011930.02086.tmb@iki.fi
AARGH...
I forgot to rediff...,
but since it seems to break the bootsplash,
the vesafb.c.diff needs more work...
but the vesafb.txt.diff should be applied...
"Thomas Backlund" <tmb@iki.fi> wrote in message
news:200306011930.02086.tmb@iki.fi...
> Here are 2 patches...
>
> The "vesafb.txt.diff" removes duplicate text in the documentation...
>
> The "vesafb.c.diff" changes the following:
> - it adds "* 2" to the video_size calculation to remap enough memory
> to do double buffering
>
> - to make sure that our double buffering calculation does not remap
> more memory than old cards actually have it uses the "old" code:
>
> if video_size > (screen_info.lfb_size * 65536)
> video_size = screen_info.lfb_size * 65536;
>
Stupid typos... :-(
I am using:
if (video_size > (screen_info.lfb_size * 65536))
video_size = screen_info.lfb_size * 65536;
> - and last but not least it changes my override to work both ways,
> so that the user can specify less or more memory to be remapped
>
>
> I earlier got a comment that this double buffering thing is not needed,
> but IMHO there will always be cards out there that are to new, so they
> dont have driver support (yet), or they are too "weird" so the only thing
> the user has to rely on is the vesafb driver, and I like the idea to get
> atleast this support "out of the box"...
>
Best Regards
Thomas
prev parent reply other threads:[~2003-06-02 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 16:30 [PATCH 2.4.21-rc6-ac1] vesafb fixes Thomas Backlund
2003-06-02 13:40 ` Thomas Backlund [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='bbfjv8$gpe$1@main.gmane.org' \
--to=tmb@iki.fi \
--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