From: "David S. Miller" <davem@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
James Simmons <jsimmons@infradead.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] Type confusion in fbcon
Date: 23 Dec 2002 13:11:43 -0800 [thread overview]
Message-ID: <1040677903.21606.0.camel@rth.ninka.net> (raw)
In-Reply-To: <Pine.GSO.4.21.0212231014460.12134-100000@vervain.sonytel.be>
On Mon, 2002-12-23 at 01:18, Geert Uytterhoeven wrote:
> That's because originally there was no fix.line_length field, and the line
> length was derived from var.xres_virtual and var.bits_per_pixel.
>
> With some hardware, the line length must be a multiple of 32 or 64 bits, and we
> needed a way to specify that, so fix.line_length was introduced. If it was
> zero, user code should fallback to the old behavior.
And with some cards, the line length is constant. Ie. to get to
"X, Y + 1" for a given "X, Y" you add a constant to your current
frame buffer pointer.
That is what fix.line_length is for right?
next prev parent reply other threads:[~2002-12-23 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 23:14 Type confusion in fbcon Russell King
2002-12-20 18:10 ` [Linux-fbdev-devel] " James Simmons
2002-12-20 21:30 ` Russell King
2002-12-23 9:18 ` Geert Uytterhoeven
2002-12-23 21:11 ` David S. Miller [this message]
2002-12-23 21:17 ` Geert Uytterhoeven
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=1040677903.21606.0.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).