From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH/RFC] atafb line length
Date: Wed, 19 Nov 2008 09:12:14 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0811190909530.27671@anakin> (raw)
In-Reply-To: <alpine.DEB.1.00.0811190757430.6915@zirkon.biophys.uni-duesseldorf.de>
On Wed, 19 Nov 2008, Michael Schmitz wrote:
> > Make sure fix->line_length is always set, as some applications need it because
> > they don't have fallback code if line_length is zero.
> >
> > Works on ARAnyM (Falcon emulation), but par->next_line is not set on any other
> > Atari variant?
>
> You're right - while testing on the Falcon framebuffer I noticed
> fix->line_length needs to be set, and kludged around to get it set to something
> more or less sane, but I could not test the other code paths.
>
> It looks like par->next_line should be set to linelen in all other decode_var
> variants. The quilt tree here does have fix->line_length = par->next_line
> already, what is your patch based on?
It was based on mainline. Yes, a part of my patch had been in my quilt series
for a while, but I wanted to post the full thing for review.
> I had
>
> fix->line_length = (par->hw.falcon.line_width + par->hw.falcon.line_offset) *
> par->hw.falcon.bpp / 8;
>
> originally - I suppose this had to change with your cfb fixes?
That should be OK. Strange, it's not what I got from you, cfr. atafb in
mainline.
Cfb16 needed
1. fix->line_length to be valid (it was zero)
2. info->pseudo_palette
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-11-19 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 21:34 [PATCH/RFC] atafb line length Geert Uytterhoeven
2008-11-17 23:01 ` Michael Schmitz
2008-11-19 7:04 ` Michael Schmitz
2008-11-19 8:12 ` Geert Uytterhoeven [this message]
2008-11-22 7:11 ` Michael Schmitz
2008-12-17 21:21 ` 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=Pine.LNX.4.64.0811190909530.27671@anakin \
--to=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitz@biophys.uni-duesseldorf.de \
/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