LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jarno Manninen <manninej@students.cc.tut.fi>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>,
	Martin Krause <Martin.Krause@tqs.de>
Subject: Re: AW: Microwindows on Icecube/CoralP
Date: Tue, 8 Feb 2005 13:23:34 +0100 (MET)	[thread overview]
Message-ID: <Pine.GSO.4.61.0502081321540.1267@waterleaf.sonytel.be> (raw)
In-Reply-To: <Pine.LNX.4.58.0502081323590.17665@mozart.cc.tut.fi>

On Tue, 8 Feb 2005, Jarno Manninen wrote:
> On Tue, 8 Feb 2005, Martin Krause wrote:
> > Hm, the SM501 has 8 MB internal RAM. The framebuffer lies within this
> > memory. The SM501 is connected with the MPC5200 over the local bus
> > interface (not over PCI) and mapped with CS1 to address range
> > 0xE0000000-0xE3FFFFFF. The SM501 configuration registers are within
> > the mapped memory area at 0xE3E00000. I can't imagine, why the byte
> > swapping should only affect accesses to the famebuffer memory and not
> > to the configuration registers (where also single bits at the right
> > position must be set correctly). I could configure CS1 to do byte
> > swapping, but then access to the SM501 configuration registers does
> > not work any longer, because this bytes are swapped, too.
> 
> Um. Have you written a kernel FB driver? If so then the write/read macros
> do this swapping for you. Assuming that you use those for accessing the
> device registers. At least SM722 requires those writes to be swapped too.

Indeed.

> > Geert, I've seen, you have done much of the fb stuff in the linux
> > kernel (thank you for that!). Could you please point me to the best
> > place, where byte swapping should be done if I want to use the linux
> > text console in 16 bit mode with the MPC5200?
> 
> Perhaps the pseudopalette would suffice here, I guess? And supposing that

Yep, text console is simple: setcolreg() must fill in the correct pixel value
in the pseudo palette. If you swap it there, it will just work.

Logo is more difficult, you need your own imageblit().

> you have written a FB driver. If not then you have to do the patching at
> the gfx-library level.

And userspace needs to do swapping as well.

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

  reply	other threads:[~2005-02-08 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 11:09 AW: Microwindows on Icecube/CoralP Martin Krause
2005-02-08 11:28 ` Jarno Manninen
2005-02-08 12:23   ` Geert Uytterhoeven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-08 14:39 Martin Krause
2005-02-08  7:33 Martin Krause
2005-02-08  8:17 ` Jarno Manninen
2005-02-08  9: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=Pine.GSO.4.61.0502081321540.1267@waterleaf.sonytel.be \
    --to=geert@linux-m68k.org \
    --cc=Martin.Krause@tqs.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=manninej@students.cc.tut.fi \
    /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