Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-29 Thread gianluca
On 06/29/2017 10:37 AM, Lucas Stach wrote: Am Mittwoch, den 28.06.2017, 18:55 +0200 schrieb gianluca: On 06/26/2017 03:28 PM, gianluca wrote: Your kernel is too old. Full support for the QuadPlus is a really recent addition. Either update your kernel to 4.12-rc, or add "clk_ignore_unused" to g

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-29 Thread Lucas Stach
Am Mittwoch, den 28.06.2017, 18:55 +0200 schrieb gianluca: > On 06/26/2017 03:28 PM, gianluca wrote: > >> > >> Your kernel is too old. Full support for the QuadPlus is a really > >> recent addition. Either update your kernel to 4.12-rc, or add > >> "clk_ignore_unused" to get at least basic function

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-26 Thread gianluca
On 06/26/2017 10:46 AM, Lucas Stach wrote: Am Montag, den 26.06.2017, 10:40 +0200 schrieb gianluca: During boot I can see no output on the framebuffer on the QuadPlus and the kernel log have those messages: [4.914737] [ cut here ] [4.914769] WARNING: CPU: 1 PID:

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-26 Thread Lucas Stach
Am Montag, den 26.06.2017, 10:40 +0200 schrieb gianluca: > On 06/23/2017 11:45 AM, gianluca wrote: > > On 06/21/2017 05:30 PM, Lucas Stach wrote: > > > > As you can see imx-drm.legacy_depth=32 is passed to the kernel > > > > from > > > > bootloader. > > > > > > The module is called "imxdrm" withou

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-26 Thread gianluca
On 06/23/2017 11:45 AM, gianluca wrote: On 06/21/2017 05:30 PM, Lucas Stach wrote: 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_d

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-23 Thread gianluca
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,

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-21 Thread Lucas Stach
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/Linu

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-21 Thread 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 S

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-21 Thread Lucas Stach
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 relea

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-21 Thread 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 a

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-20 Thread Sascha Hauer
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 Bar

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-06-19 Thread gianluca
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 a

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-02-21 Thread gianluca
On 02/21/2017 04:03 PM, Lucas Stach wrote: 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 no

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-02-21 Thread gianluca
On 02/21/2017 02:04 PM, gianluca wrote: 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 wit

Re: Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-02-21 Thread Lucas Stach
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

Fwd: Barebox 2017.02 works great but no Linux Framebuffer... :-/

2017-02-21 Thread 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