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 17:30:09 +0200	[thread overview]
Message-ID: <1498059009.2904.108.camel@pengutronix.de> (raw)
In-Reply-To: <3f12f02e-cccc-1edb-94d1-8cff2b69c808@eurekelettronica.it>

Am Mittwoch, den 21.06.2017, 17:18 +0200 schrieb gianluca:
> On 06/21/2017 01:50 PM, Lucas Stach wrote:
> 
> > 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".
> >
> 
> >
> > Debian GNU/Linux 8 edelin ttymxc2
> >
> > edelin login: root
> > Password:
> > Linux edelin 4.9.7-EK20170621 #1 SMP Wed Jun 21 15:23:57 CEST 2017 armv7l
> >
> > The programs included with the Debian GNU/Linux system are free software;
> > the exact distribution terms for each program are described in the
> > individual files in /usr/share/doc/*/copyright.
> >
> > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> > permitted by applicable law.
> > root@edelin:~# fbset
> >
> > mode "1280x800"
> >     geometry 1280 800 1280 800 16
> >     timings 0 0 0 0 0 0 0
> >     accel true
> >     rgba 5/11,6/5,5/0,0/0
> > endmode
> >
> > root@edelin:~# cat /proc/cmdline
> > 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 imx-drm.legacyfb_depth=32
> 
> As you can see imx-drm.legacy_depth=32 is passed to the kernel from 
> bootloader.

The module is called "imxdrm" without a dash, so the correct way to
specify the parameter on the command line is "imxdrm.legacyfb_depth=32".

I'm not sure what you are trying to achieve with the mxcfb and fbmem
parameters. They are certainly ignored by a mainline kernel.

Regards,
Lucas


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

  reply	other threads:[~2017-06-21 15:30 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
2017-06-21 15:18             ` gianluca
2017-06-21 15:30               ` Lucas Stach [this message]
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=1498059009.2904.108.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