public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Petr Stehlik <pstehlik@sophics.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH/RFC] atafb and panning
Date: Wed, 19 Nov 2008 09:51:35 +0100	[thread overview]
Message-ID: <1227084695.8542.14.camel@petr> (raw)
In-Reply-To: <Pine.LNX.4.64.0811190912190.27671@anakin>

Geert Uytterhoeven píše v St 19. 11. 2008 v 09:15 +0100:
> > par->hw.falcon.xoffset takes care of that, and xoffset takes care of the rest. 
> > Since the partial word offset shifts the beginnig of the scan line into the 
> > first word, the offset to the next scan line (par->hw.falcon.line_offset) has to 
> > be shortened. 
> 
> Sounds reasonable. But the shortening part doesn't work on ARAnyM, nor do
> small panning increments. So it really smells like an ARAnyM bug.

I guess this is about horizontal scrolling which was used in old 2D
games only and frankly, we don't have many games running on ARAnyM (it's
not the goal of ARAnyM project, anyway). I hacked the VIDEL emulation
many years ago just to get the TOS booting and even though it's been
improved by others since then it's likely nobody run into this yet.

Just please tell me if the xoffset you mention is the 0xff8264 register
or if I am completely out. And for now write the linux kernel according
to the HW docs and I'll then correct the VIDEL emulation to do the right
thing in fbtests :-)

Thanks :)

Petr

P.S. There is a new release of ARAnyM in sid since last week (that has
the special "--halt" option for Stephen and other installing
Debian/m68k :-) but I am willing to do another release as soon as this
probable/apparent VIDEL deficiency is fixed.


--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-11-19  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 21:36 [PATCH/RFC] atafb and panning Geert Uytterhoeven
2008-11-16 23:22 ` Petr Stehlík
2008-11-19  7:37 ` Michael Schmitz
2008-11-19  8:15   ` Geert Uytterhoeven
2008-11-19  8:51     ` Petr Stehlik [this message]
2008-11-22  7:16     ` Michael Schmitz
2008-11-22  8:45       ` Petr Stehlík
2008-11-23 13:03         ` Geert Uytterhoeven
     [not found]         ` <1227379735.6118.10.camel@joy>
     [not found]           ` <Pine.LNX.4.64.0811232242480.30025@anakin>
     [not found]             ` <alpine.DEB.1.00.0811240050090.15319@zirkon.biophys.uni-duesseldorf.de>
     [not found]               ` <Pine.LNX.4.64.0812141725090.5936@anakin>
     [not found]                 ` <alpine.DEB.1.00.0812150457400.29644@zirkon.biophys.uni-duesseldorf.de>
2008-12-16 20:49                   ` atari_mouse_interrupt_hook (was: Re: [PATCH/RFC] atafb and panning) Geert Uytterhoeven
2008-12-17  1:13                     ` Michael Schmitz
2008-11-23  2:38     ` [PATCH/RFC] atafb and panning Michael Schmitz
2008-11-23 10:34       ` fbtest (was: Re: [PATCH/RFC] atafb and panning) Geert Uytterhoeven
2008-11-23 23:05         ` Michael Schmitz

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=1227084695.8542.14.camel@petr \
    --to=pstehlik@sophics.cz \
    --cc=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