mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: gianluca <gianlucarenzi@eurekelettronica.it>
Cc: barebox@lists.infradead.org
Subject: Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/
Date: Wed, 21 Jun 2017 13:50:32 +0200	[thread overview]
Message-ID: <1498045832.2904.105.camel@pengutronix.de> (raw)
In-Reply-To: <126e2527-f179-0c82-c384-c6c975a7c8e9@eurekelettronica.it>

Am Mittwoch, den 21.06.2017, 13:35 +0200 schrieb gianluca:
> On 06/21/2017 08:32 AM, Sascha Hauer wrote:
> > Hi Gianluca,
> >
> > On Mon, Jun 19, 2017 at 05:49:41PM +0200, gianluca wrote:
> >> Hello Lucas, Sascha and the barebox mailing list guys!
> >>
> >> I am back with the new boards batch release (now QuadPlus and DualLite iMX6)
> >>
> >> Now I adapted barebox to fit both processors and it works quite well.
> >>
> >> From Barebox point-of-view the ldb node of the device-tree is using three
> >> timings and they are working good depending on which panel bridge board I am
> >> connecting to (1280x800, 1024x600 and 800x480).
> >>
> >> The custom startup code of barebox is looking for a special eeprom on the
> >> panel-bridge and set the device tree accordingly, i.e. setting the
> >> native-mode node to the correct display-timing.
> >>
> >> The same device-tree is used in Linux (as in attachment) as you can see the
> >> ldb section and the panel section, using a simple-panel and a correct panel
> >> timing using the innolux,g101ice_l01 panel driver timings.
> >>
> >>>
> >>>> No, Linux does not support DT defined modes in the panel. You need a
> >>>> panel with a proper compatible and driver.
> >>>>
> >>>> See drivers/gpu/drm/panel. For most LVDS panels simple-panel is what you
> >>>> want to use.
> >>>>
> >>
> >> They are ignored in the Barebox starup (as you know barebox can use the
> >> display-timings in the ldb section) but the panel section is used in linux.
> >>
> >> Nevertheless it does not work.
> >
> > What exactly does not work? No picture in barebox? Any error messages?
> > Does it work in Linux?
> >
> 
> In Barebox no problem at all (screen frequency apart. For every 
> display-timing found it gives me @0 Hz...).
> 
> The problem is in Linux. The utility fbset is giving me 16bpp!!
> 
> The panel driver used (innolux,g101ice-l01) has the RGB888 format and 
> the ldb in the device-tree section has fsl,data-width = <24>
> 
> This issue is present for every panel I use (lg,lb070wv8 and 
> auo,b101aw03 too) so maybe some misconfiguration somewhere...
> 
> I was supposed to have 24 or 32 bit in the framebuffer driver using 
> fbset... May be some fbset issue?
> 
> Some issue??? I have no Xorg. only fbdev

The fbdev emulation in the imx-drm driver defaults to 16bpp. If you want
to change this you need to provide the module parameter
"legacyfb_depth=32".

Regards,
Lucas


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-06-21 11:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <63687e34-f354-81d3-aed7-1a59866925c5@eurekelettronica.it>
2017-02-21 13:04 ` gianluca
2017-02-21 14:56   ` gianluca
2017-02-21 15:03   ` Lucas Stach
2017-02-21 17:59     ` gianluca
2017-06-19 15:49     ` gianluca
2017-06-21  6:32       ` Sascha Hauer
2017-06-21 11:35         ` gianluca
2017-06-21 11:50           ` Lucas Stach [this message]
2017-06-21 15:18             ` gianluca
2017-06-21 15:30               ` Lucas Stach
2017-06-23  9:45                 ` gianluca
2017-06-26  8:40                   ` gianluca
2017-06-26  8:46                     ` Lucas Stach
2017-06-26 13:28                       ` gianluca
2017-06-28 16:55                         ` gianluca
2017-06-29  8:37                           ` Lucas Stach
2017-06-29 10:07                             ` gianluca

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=1498045832.2904.105.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=gianlucarenzi@eurekelettronica.it \
    /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