From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: "Ville Syrjälä" <syrjala@sci.fi>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [Question] Colour management
Date: Sun, 1 Aug 2004 07:47:43 +0800 [thread overview]
Message-ID: <200408010747.43233.adaplas@hotpop.com> (raw)
In-Reply-To: <20040731221858.GA17721@sci.fi>
On Sunday 01 August 2004 06:18, Ville Syrjälä wrote:
> On Sat, Jul 31, 2004 at 06:26:27PM +0800, Antonino A. Daplas wrote:
> > On Saturday 31 July 2004 02:12, Alexander Kern wrote:
> > > Hallo Tony,
> > >
> > > can you explain the deep mining of fb_setcolreg. Background, I observe
> > > wrong palette using in 15 and 16 bpp modes, but can not understand,
> > > what is the right approach. In both cases from penguin logo I can see
> > > only contour in honey yellow and blue vertical string jsimmons, pretty
> > > scury ;-) The rest is black! The simple text or ncurses applications
> > > have always right colours. Additionally and only by 16bpp fbi shows
> > > blurry images. In 15bpp fbi works fine. fbtest works fine and his
> > > penguins look good in all resolutions ?!
> >
> > This will need a long answer. (For mistakes or ommisions, please let me
> > know)
> >
> > fb_setcolreg has 2 functions, initialize info->pseudopalette (if needed)
> > and initialize the hardware CLUT (if needed).
>
> BTW fb_setcolreg ends up writing half of the registers twice (more if you
> have to fill all slots). It might be better to have two functions. The
> first one would be the current fb_setcolreg except it wouldn't actually
> write anything. It would only fill in the correct register values. And the
> second one would write the clut to hardware. That would avoid the multiple
> writes.
Yes, we also need to separate the imageblit into a mono_src_color_expand
(for text drawing) and an 8_bit_src_color_expand (for the logo). Both proposals
will affect all drivers so let's leave it as is for now (unless you want to risk
the ire again of the fbdev driver maintainers, they're a bit touchy from the
numerous breakages of the API :-)
Tony
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-07-31 23:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 18:49 [PATCH] atyfb: vblank irq support Ville Syrjälä
2004-07-24 23:12 ` Alexander Kern
2004-07-25 0:03 ` Antonino A. Daplas
2004-07-25 18:36 ` Alexander Kern
2004-07-25 22:47 ` Antonino A. Daplas
2004-07-30 18:12 ` [Question] Colour management Alexander Kern
2004-07-31 10:26 ` Antonino A. Daplas
2004-07-31 13:31 ` Ville Syrjälä
2004-07-31 21:19 ` Antonino A. Daplas
2004-07-31 22:19 ` Alexander Kern
2004-07-31 23:37 ` Antonino A. Daplas
2004-07-31 22:18 ` Ville Syrjälä
2004-07-31 23:47 ` Antonino A. Daplas [this message]
2004-07-31 22:10 ` Ville Syrjälä
2004-08-01 1:03 ` Antonino A. Daplas
2004-07-25 10:16 ` [PATCH] atyfb: vblank irq support Ville Syrjälä
2004-07-25 18:29 ` Alexander Kern
2004-07-25 23:36 ` Ville Syrjälä
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=200408010747.43233.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=syrjala@sci.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;
as well as URLs for NNTP newsgroup(s).