From: Paulo Marques <pmarques@grupopie.com>
To: "Hans-Jürgen Koch" <hjk@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-fbdev-devel@lists.sourceforge.net,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] pxafb: Add support for other palette formats
Date: Tue, 03 Jul 2007 18:21:38 +0100 [thread overview]
Message-ID: <468A85A2.1070506@grupopie.com> (raw)
In-Reply-To: <200707031845.57256.hjk@linutronix.de>
Hans-Jürgen Koch wrote:
> Am Dienstag 03 Juli 2007 18:03 schrieb Paulo Marques:
>> [...]
>> Or maybe teach fbcon to use 18bpp modes?
>
> This would only make sense if this is a common format that other
> chips use, too.
I don't see this as a good reason not to implement 18bpp support in
fbcon. "Just PXA270 18bpp devices" can be a lot of devices out there.
Anyway, can fbcon work with 18bpp palette mode? If it does, then this
should be enough for most users of 18bpp pxafb users: have a console
with a palette mode and then switch to non-palette mode and run whatever
windowing system supports 18bpp.
I guess that even if it doesn't support 18bpp palette mode now, it
shouldn't be that hard to implement (nor should it cause that much bloat
to fbcon).
>>> BTW: PXA255 doesn't have an LCCR4 register.
>> If we make sure that we don't touch LCCR4 registers unless the platform
>> driver asks for 18bpp we should be in the clear, no?
>>
>> However, the current patch does write to LCCR4 without checking this,
>> but this should be a no-op if there is no register there, AFAICS.
>
> Arrg, no, you can't do this. Even if it works on your current PXA255
> revision, writing to a nonexistent register is certainly not something
> we should do in a proper driver.
Yes, I wasn't proposing that this be kept (that would be waaay too
ugly), only pointing out that it shouldn't crash existing setups.
>> I'll try to handle it more correctly in my next patch, anyway.
>
> So will I. I'll update my patch.
Ok.
--
Paulo Marques - www.grupopie.com
"God is real, unless declared integer."
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2007-07-03 17:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 14:07 [PATCH] pxafb: Add support for other palette formats Hans-Jürgen Koch
2007-07-03 14:46 ` Paulo Marques
2007-07-03 15:03 ` Hans-Jürgen Koch
2007-07-03 15:24 ` Paulo Marques
2007-07-03 15:50 ` Lothar Wassmann
2007-07-03 15:58 ` Geert Uytterhoeven
2007-07-12 7:56 ` Antonino A. Daplas
2007-07-12 8:01 ` Antonino A. Daplas
2007-07-03 16:03 ` Paulo Marques
2007-07-03 16:45 ` Hans-Jürgen Koch
2007-07-03 17:21 ` Paulo Marques [this message]
2007-07-03 17:44 ` Hans-Jürgen Koch
2007-07-03 18:18 ` Paulo Marques
2007-07-04 7:17 ` Lothar Wassmann
2007-07-04 11:00 ` Paulo Marques
2007-07-04 6:56 ` Lothar Wassmann
2007-07-03 16:39 ` Hans-Jürgen Koch
2007-07-03 17:14 ` Lothar Wassmann
2007-07-03 17:33 ` Hans-Jürgen Koch
2007-07-13 12:20 ` Antonino A. Daplas
2007-07-13 12:39 ` Hans-Jürgen Koch
2007-07-03 19:01 ` Clemens Koller
2007-07-03 19:11 ` Hans-Jürgen Koch
2007-07-03 20:36 ` Hans-Jürgen Koch
2007-07-04 6:38 ` eric miao
2007-07-04 7:51 ` Lothar Wassmann
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=468A85A2.1070506@grupopie.com \
--to=pmarques@grupopie.com \
--cc=hjk@linutronix.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.