| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20130524081156.GA3154@lukather>
Date: Fri, 24 May 2013 10:11:56 +0200
From: "maxime.ripard@...e-electrons.com" <maxime.ripard@...e-electrons.com>
To: Juergen Beisert <jbe@...gutronix.de>
Cc: linux-arm-kernel@...ts.infradead.org,
Hector Palacios <hector.palacios@...i.com>,
"fabio.estevam@...escale.com" <fabio.estevam@...escale.com>,
brian@...stalfontz.com, s.hauer@...gutronix.de,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Subject: Re: mxsfb: DATA_FORMAT_24_BIT flag outputs invalid colours
Hi Juergen,
On Thu, May 23, 2013 at 03:31:31PM +0200, Juergen Beisert wrote:
> Hi Maxime,
>
> maxime.ripard@...e-electrons.com wrote:
> > On Thu, May 23, 2013 at 01:55:28PM +0200, Hector Palacios wrote:
> > > I'm using an i.MX28 based board with lcd connected with 18bits data bus.
> > > My platform uses 32 bits per pixel:
> > >
> > > mxsfb_pdata.default_bpp = 32;
> > > mxsfb_pdata.ld_intf_width = STMLCDIF_18BIT;
> > >
> > > With these settings the mxsfb.c driver sets flag DATA_FORMAT_24_BIT
> > > at HW_LCDIF_CTRL register in function mxsfb_set_par():
> > >
> > > case 32:
> > > dev_dbg(&host->pdev->dev, "Setting up RGB888/666 mode\n");
> > > ctrl |= CTRL_SET_WORD_LENGTH(3);
> > > switch (host->ld_intf_width) {
> > > case STMLCDIF_8BIT:
> > > dev_dbg(&host->pdev->dev,
> > > "Unsupported LCD bus width mapping\n");
> > > return -EINVAL;
> > > case STMLCDIF_16BIT:
> > > case STMLCDIF_18BIT:
> > > /* 24 bit to 18 bit mapping */
> > > ctrl |= CTRL_DF24; /* ignore the upper 2 bits in
> > > * each colour component
> > > */
> > > break;
> > > case STMLCDIF_24BIT:
> > > /* real 24 bit */
> > > break;
> > > }
> > >
> > > According to the manual, this flag does:
> > > 0x0: ALL_24_BITS_VALID: Data input to the block is in 24 bpp
> > > format, such that all RGB 888 data is contained in 24 bits.
> > > 0x1: DROP_UPPER_2_BITS_PER_BYTE — Data input to the block is
> > > actually RGB 18 bpp, but there is 1 colour per byte, hence the upper
> > > 2 bits in each byte do not contain any useful data, and should be
> > > dropped.
> > >
> > > The setting of this flag is producing bad colours with true colour
> > > images (i.e. the Linux penguin is displayed ok, but QT applications
> > > or images displayed with fbv are not).
> > > I believe the setting of this flag is not correct (after all, if my
> > > bpp is 32, then all 24bit colours are useful and dropping the upper
> > > 2 bits is a bad idea).
> > > If I don't set it, then true colour images are displayed correctly.
> > > The only problem is that the Linux penguin is displayed much darker
> > > than usual (correct colours, but darker). Perhaps the 224 colour
> > > format of this image justifies it?
> > >
> > > I noticed the cfa10049 platform also uses the same configuration (18
> > > bits data bus and 32bpp) and was wondering if true colour images are
> > > correctly displayed in this platform with this flag set (for example
> > > with fbv application [1]).
> >
> > I had the exact same problem, and suggested the exact same solution a
> > few weeks back.
> >
> > https://patchwork.kernel.org/patch/2470441/
> >
> > The conclusion of that discussion what that the userspace applications
> > were not honouring the bitfield correctly set by the mxsfb driver, and
> > as such, it was not a bug in the driver.
> >
> > While this is correct, I wonder, now that since we had that same problem
> > in a very short amount of time, if we couldn't set this behaviour
> > dependant of some (dt? kernel argument?) property so that one could
> > customise it anyway he want.
> >
> > Maxime
>
> i.MX2[3|8] LCD1 LCD2 LCD3
> 24bit 18bit 18bit
> --------------------------------------------
> LCD_D0 B0 B0 --
> LCD_D1 B1 B1 --
> LCD_D2 B2 B2 B0
> LCD_D3 B3 B3 B1
> LCD_D4 B4 B4 B2
> LCD_D5 B5 B5 B3
> LCD_D6 B6 G0 B4
> LCD_D7 B7 G1 B5
>
> LCD_D8 G0 G2 --
> LCD_D9 G1 G3 --
> LCD_D10 G2 G4 G0
> LCD_D11 G3 G5 G1
> LCD_D12 G4 R0 G2
> LCD_D13 G5 R1 G3
> LCD_D14 G6 R2 G4
> LCD_D15 G7 R3 G5
>
> LCD_D16 R0 R4 --
> LCD_D17 R1 R5 --
> LCD_D18 R2 R0
> LCD_D19 R3 R1
> LCD_D20 R4 R2
> LCD_D21 R5 R3
> LCD_D22 R6 R4
> LCD_D23 R7 R5
>
> Is your display connected like LCD2 or LCD3? LCD3 must still handled like a 24
> bit display shown in LCD1, while only the LCD2-case is the "24 bit to 18 bit
> mapping" case.
>
> At least my current tests with an i.MX23 and a connection like LCD2 are
> working here with a Qt application. Qt honours the pixel bitfield
> description. And I'm using the "bits-per-pixel = <32>" and "bus-width = <18>"
> entries in the device tree.
I'm in the second case, so with the same setup that you have it seems.
Don't get me wrong, I was not saying that the driver was flawed or had a
bug, I understood very well your arguments when I first submitted the
patch. The problem is more for all the userspace applications that don't
honour the bitfield and just look at the color depth used to feed data
to the framebuffer.
I must admit that the ideal case should be that these applications
should be fixed, but it's not realistic.
About QT, let's not use it as an example, the issues I had were probably
some miscompilation on my side, and if you say that it works fine, then
I trust you.
This is also why I suggested a kernel argument to enable a different
"compatibility" mode when you have to deal with these kind of
applications on your system. the pixel bitfield should probably be
changed as well so that applications honouring it are not confused.
Hector's case looks like a different story though.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists