From: gianluca <gianlucarenzi@eurekelettronica.it>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/
Date: Fri, 23 Jun 2017 11:45:31 +0200 [thread overview]
Message-ID: <aaba2d2b-6d53-07a7-bfdd-f70c22ad13c6@eurekelettronica.it> (raw)
In-Reply-To: <1498059009.2904.108.camel@pengutronix.de>
On 06/21/2017 05:30 PM, Lucas Stach wrote:
> Am Mittwoch, den 21.06.2017, 17:18 +0200 schrieb gianluca:
>> On 06/21/2017 01:50 PM, Lucas Stach wrote:
>>> 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.
>
It works now, the culprit was the name of the driver: imxdrm is the
right one.
Now a little bit off-topic question:
- Is it better to use Xorg X11 (with a custom full screen application
using Qt 5) [with all concerns about using a Debian Jessie for armhf,
i.e.: imx-drm-vivante driver, opengl/opencl custom libraries etc.,...]
or using a framebuffer Qt application??? I know the framebuffer does not
have any acceleration, but I suppose the CPU (even the dual-core) is
powerful enough to manage some simple transition of the application pages...
What do you think about this?
Regards,
--
Eurek s.r.l. |
Electronic Engineering | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377 | Fax: +39-(0)542-609212
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-06-23 9:46 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
2017-06-23 9:45 ` gianluca [this message]
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=aaba2d2b-6d53-07a7-bfdd-f70c22ad13c6@eurekelettronica.it \
--to=gianlucarenzi@eurekelettronica.it \
--cc=barebox@lists.infradead.org \
--cc=l.stach@pengutronix.de \
/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