From: Thomas Backlund <tmb@iki.fi>
To: Willy TARREAU <willy@w.ods.org>
Cc: Willy Tarreau <willy@w.ods.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4.21-rc1] vesafb with large memory
Date: Tue, 6 May 2003 03:21:23 +0300 [thread overview]
Message-ID: <200305060321.23459.tmb@iki.fi> (raw)
In-Reply-To: <20030504094900.GA342@pcw.home.local>
Viestissä Sunnuntai 4. Toukokuuta 2003 12:49, Willy TARREAU kirjoitti:
> Hi Thomas,
>
> > the correct line should AFAIK be:
> > video_size = screen_info.lfb_width * screen_info.lfb_height *
> > video_bpp;
> >
> > (AFAIK we are calculating bits here, not bytes so the '/8' you used is
> > wrong... could you try without it, and let me know...)
>
> No, after verification, I insist, we're really calculating BYTES here.
> Please take a look :
Yes,
you are right...
[...]
>
> So I think that the correct line really is :
> video_size = screen_info.lfb_width * screen_info.lfb_height *
> video_bpp / 8;
There is a problem with this, ...
If we calculate the exact memory like this, there wont be any
memory remapped to do double/tripple buffering...
So the question is: shoud one take the formula and add ' * 2' to
atleast get the double buffering supported...
(in the patch I made for mdk, I kept a modified override part so that
the user can change this, if he needs it....)
Alan,
any comments on this?
> (Which also handles line widths which are not multiple of 8).
Well actually, in that formula it does not matter where you put the '/8',
the result is always the same...
> BTW, I wonder why we truncate the mtrr size to the highest lower power
> of 2. Shouldn't we round it up to the next one ?
>
Isn't it a hardware requirement?
I think I read it in a nvidia document once...
(of course they may be wrong...)
--
Thomas Backlund
tmb@iki.fi
www.iki.fi/tmb
next prev parent reply other threads:[~2003-05-06 0:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 21:33 O.Sezer
2003-05-01 12:00 ` Thomas Backlund
2003-05-01 12:07 ` Alan Cox
2003-05-01 15:01 ` Thomas Backlund
2003-05-01 14:49 ` Alan Cox
2003-05-01 17:39 ` Thomas Backlund
2003-05-02 0:14 ` Thomas Backlund
2003-05-02 13:03 ` Willy Tarreau
2003-05-03 12:46 ` Thomas Backlund
2003-05-03 21:58 ` Willy Tarreau
2003-05-04 9:49 ` Willy TARREAU
2003-05-06 0:21 ` Thomas Backlund [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 15:58 Walt H
2003-05-01 14:20 O.Sezer
2003-05-01 15:03 ` Thomas Backlund
2003-05-01 15:09 ` O.Sezer
2003-04-30 18:58 O.Sezer
2003-04-30 8:09 Adam Mercer
2003-04-30 11:26 ` Alan Cox
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=200305060321.23459.tmb@iki.fi \
--to=tmb@iki.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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
Powered by JetHome