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: Tue, 21 Feb 2017 16:03:00 +0100	[thread overview]
Message-ID: <1487689380.2268.18.camel@pengutronix.de> (raw)
In-Reply-To: <2f43179e-2aa0-1dba-eafa-a9c0025afd24@eurekelettronica.it>

Am Dienstag, den 21.02.2017, 14:04 +0100 schrieb gianluca:
> Hello everybody!
> 
> I am fighting to enable ldb in Linux 4.9.7. In barebox the SAME 
> device-tree is modified by barebox to enable/disable the ldb or hdmi 
> depending on what is found.
> 
> During Linux bootup with HDMI only, it works with no hassle.
> 
> If booting with ldb it does not start the ldb driver registration due to 
> a panel/bridge missing.
> 
> In the config of linux kernel I have (as imx_v6_v7_defconfig) all drm 
> and simple panel enabled.
> 
> What is missing???
> 
> Best regards,
> Gianluca
> 
> -------- Forwarded Message --------
> Subject: Barebox 2017.02 works great but no Linux Framebuffer... :-/
> Date: Mon, 20 Feb 2017 16:36:06 +0100
> From: gianluca <gianlucarenzi@eurekelettronica.it>
> To: Sascha Hauer <s.hauer@pengutronix.de>
> 
> Hello Sascha,
> 
> During last week I was able to activate/deactivate the hdmi and ldb 
> nodes from internal device-tree of Barebox and everything is working great.
> 
> Now I would like to boot up with the kernel 4.9.7 with the following 
> commandline but it fails.
> 
> The kernelcmd line is:
> 
> > console=ttymxc2,115200 rootwait noswap ip=none noinitrd rootfstype=nilfs2 root=/dev/mmcblk1p3 fec.macaddr=0x7a,0x3f,0x03,0xe3,0xa2,0xff system_rev=0xe3600000 system_serialnr=0x00000000 lcd_type=am1280800n3tz fastboot quiet loglevel=3 console=tty0  video=mxcfb0:dev=ldb,if=RGB24,bpp=32 fbmem=32M vmalloc=400M
> 
> The problem is the ldb (imx-ldb.c you wrote in kernel 
> drivers/gpu/drm/imx...). It fails with the following error:
> 
> > [    7.526349] imx-ldb 2000000.aips-bus:ldb@020e0008: panel/bridge not found: /panel --
> > [    7.526369] imx-drm display-subsystem: failed to bind 2000000.aips-bus:ldb@020e0008 (ops 0xc097aaa0): -517
> > [    7.526785] imx-drm display-subsystem: master bind failed: -517
> 
> The device-tree is attached.
> 
> The device tree is the same as Barebox (it has only an #included 
> commented out).
> 
> Both hdmi and ldb nodes are initially left "disabled" then barebox 
> enable the node corresponding to the hardware found (i.e. it changes the 
> status to "okay")
> 
> In barebox everything is working.
> 
> In linux NOT. What is exactly a 'channel->bridge' and 'channel->panel' 
> in device-tree therminology?
> 
> Barebox is working without it, so I suppose it was working in Linux 
> kernel too...

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.

Regards,
Lucas


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

  parent reply	other threads:[~2017-02-21 15:03 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 [this message]
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
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=1487689380.2268.18.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