From: Gerd Knorr <kraxel@bytesex.org>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [Linux-fbdev-devel] Re: [PATCH] vesafb memory size mismatch
Date: Mon, 4 Oct 2004 11:27:30 +0200 [thread overview]
Message-ID: <20041004092730.GA4552@bytesex> (raw)
In-Reply-To: <200410020422.15936.adaplas@hotpop.com>
> > + /* size_total -- all video memory we have. Used for mtrr
> > + * entries and bounds checking. */
> > + size_total = screen_info.lfb_size * 65536;
> > + if (size_total < size_vmode)
> > + size_total = size_vmode;
> > + if (vram)
> > + size_total = vram * 1024 * 1024;
> Probably a typo, but shouldn't it be...
>
> size_remap = size_vmode * 2;
> if (vram)
> size_remap = vram * 1024 * 1024;
> if (size_remap > size_total)
> size_remap = size_total
No, it's intentional. Some bioses seem to report bogous values for the
total amount of memory, so you can use vram to fixup that. The
"size_total < size_vmode" check which is kida silly is there for the
very same reason: on a bug-free bios it should never ever trigger, but
looks like it is needed neverless.
We might want to add another parameter to allow the user to adjust
size_remap through. I'll prepare an updated patch one later today,
with other issue (line_length != width * depth) fixed as well.
Gerd
--
return -ENOSIG;
next prev parent reply other threads:[~2004-10-04 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 13:36 [PATCH] vesafb memory size mismatch Aurelien Jacobs
2004-10-01 15:48 ` Gerd Knorr
2004-10-01 20:22 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-04 9:27 ` Gerd Knorr [this message]
2004-10-03 0:53 ` Aurelien Jacobs
2004-10-03 1:59 ` Andrew Morton
2004-10-03 8:46 ` Antonino A. Daplas
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=20041004092730.GA4552@bytesex \
--to=kraxel@bytesex.org \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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).