* Re: HDMI doesn't work on ULCB board [not found] <87bm7svwmp.wl-kuninori.morimoto.gx@renesas.com> @ 2018-10-19 13:32 ` Laurent Pinchart 2018-10-29 1:07 ` Kuninori Morimoto 2018-11-06 14:30 ` Laurent Pinchart 1 sibling, 1 reply; 9+ messages in thread From: Laurent Pinchart @ 2018-10-19 13:32 UTC (permalink / raw) To: Kuninori Morimoto; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Morimoto-san, On Thursday, 18 October 2018 05:12:14 EEST Kuninori Morimoto wrote: > Hi Vladimir, Laurent > > I'm testing ULCB board, and I noticed that HDMI doen't work on it. Which ULCB board is this ? > - Sometimes kernel panic happen (I lost log, but it said "get crc" > something error), - Often, kernel doesn't boot with below log if I > connected HDMI cable when booting > - Monitor say "No signal" if I connected cable *after* booting > > I'm using Geert's renesas-drivers-2018-10-09-v4.19-rc7 branch. > It seems salvator HDMI is working correctly on it. > I attached my .config > > ------ kernel log --------- > ... > [ 1.728010] renesas_irqc e61c0000.interrupt-controller: driving 6 irqs > [ 1.739166] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 1.745851] [drm] No driver support for vblank timestamp query. > [ 1.787533] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 1.794226] [drm] No driver support for vblank timestamp query. > [ 1.821091] rcar-dmac e6700000.dma-controller: ignoring dependency for > device, assuming no driver > [ 1.835807] rcar-dmac e7300000.dma-controller: ignoring dependency for > device, assuming no driver > [ 1.850397] rcar-dmac e7310000.dma-controller: ignoring dependency for > device, assuming no driver > [ 1.864799] rcar-dmac ec700000.dma-controller: ignoring dependency for > device, assuming no driver > [ 1.879168] rcar-dmac ec720000.dma-controller: ignoring dependency for > device, assuming no driver > [ 1.894102] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 1.900788] [drm] No driver support for vblank timestamp query. > [ 1.907851] ravb e6800000.ethernet: ignoring dependency for device, > assuming no driver > [ 1.917038] libphy: ravb_mii: probed > [ 1.922342] ravb e6800000.ethernet eth0: Base address at 0xe6800000, > 2e:09:0a:00:83:2b, IRQ 116. > [ 1.931494] rcar-fcp fe950000.fcp: ignoring dependency for device, > assuming no driver > [ 1.939736] rcar-fcp fe951000.fcp: ignoring dependency for device, > assuming no driver > [ 1.947894] rcar-fcp fe96f000.fcp: ignoring dependency for device, > assuming no driver > [ 1.956044] rcar-fcp fe92f000.fcp: ignoring dependency for device, > assuming no driver > [ 1.964206] rcar-fcp fe9af000.fcp: ignoring dependency for device, > assuming no driver > [ 1.972359] rcar-fcp fe9bf000.fcp: ignoring dependency for device, > assuming no driver > [ 1.980517] rcar-fcp fea27000.fcp: ignoring dependency for device, > assuming no driver > [ 1.988669] rcar-fcp fea2f000.fcp: ignoring dependency for device, > assuming no driver > [ 1.996825] rcar-fcp fea37000.fcp: ignoring dependency for device, > assuming no driver > [ 2.040729] rcar_sound ec500000.sound: probed > [ 2.045763] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 2.052441] [drm] No driver support for vblank timestamp query. > /* here kernel stop */ I will have a look. -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: HDMI doesn't work on ULCB board 2018-10-19 13:32 ` HDMI doesn't work on ULCB board Laurent Pinchart @ 2018-10-29 1:07 ` Kuninori Morimoto 0 siblings, 0 replies; 9+ messages in thread From: Kuninori Morimoto @ 2018-10-29 1:07 UTC (permalink / raw) To: Laurent Pinchart; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Laurent > > I'm testing ULCB board, and I noticed that HDMI doen't work on it. > > Which ULCB board is this ? I'm using R-Car H3 v2.0 ULCB board. > > ------ kernel log --------- > > ... > > [ 1.728010] renesas_irqc e61c0000.interrupt-controller: driving 6 irqs > > [ 1.739166] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > > [ 1.745851] [drm] No driver support for vblank timestamp query. > > [ 1.787533] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > > [ 1.794226] [drm] No driver support for vblank timestamp query. > > [ 1.821091] rcar-dmac e6700000.dma-controller: ignoring dependency for > > device, assuming no driver > > [ 1.835807] rcar-dmac e7300000.dma-controller: ignoring dependency for > > device, assuming no driver > > [ 1.850397] rcar-dmac e7310000.dma-controller: ignoring dependency for > > device, assuming no driver > > [ 1.864799] rcar-dmac ec700000.dma-controller: ignoring dependency for > > device, assuming no driver > > [ 1.879168] rcar-dmac ec720000.dma-controller: ignoring dependency for > > device, assuming no driver > > [ 1.894102] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > > [ 1.900788] [drm] No driver support for vblank timestamp query. > > [ 1.907851] ravb e6800000.ethernet: ignoring dependency for device, > > assuming no driver > > [ 1.917038] libphy: ravb_mii: probed > > [ 1.922342] ravb e6800000.ethernet eth0: Base address at 0xe6800000, > > 2e:09:0a:00:83:2b, IRQ 116. > > [ 1.931494] rcar-fcp fe950000.fcp: ignoring dependency for device, > > assuming no driver > > [ 1.939736] rcar-fcp fe951000.fcp: ignoring dependency for device, > > assuming no driver > > [ 1.947894] rcar-fcp fe96f000.fcp: ignoring dependency for device, > > assuming no driver > > [ 1.956044] rcar-fcp fe92f000.fcp: ignoring dependency for device, > > assuming no driver > > [ 1.964206] rcar-fcp fe9af000.fcp: ignoring dependency for device, > > assuming no driver > > [ 1.972359] rcar-fcp fe9bf000.fcp: ignoring dependency for device, > > assuming no driver > > [ 1.980517] rcar-fcp fea27000.fcp: ignoring dependency for device, > > assuming no driver > > [ 1.988669] rcar-fcp fea2f000.fcp: ignoring dependency for device, > > assuming no driver > > [ 1.996825] rcar-fcp fea37000.fcp: ignoring dependency for device, > > assuming no driver > > [ 2.040729] rcar_sound ec500000.sound: probed > > [ 2.045763] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > > [ 2.052441] [drm] No driver support for vblank timestamp query. > > /* here kernel stop */ > > I will have a look. Thanks ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: HDMI doesn't work on ULCB board [not found] <87bm7svwmp.wl-kuninori.morimoto.gx@renesas.com> 2018-10-19 13:32 ` HDMI doesn't work on ULCB board Laurent Pinchart @ 2018-11-06 14:30 ` Laurent Pinchart 2018-11-06 15:40 ` Laurent Pinchart 1 sibling, 1 reply; 9+ messages in thread From: Laurent Pinchart @ 2018-11-06 14:30 UTC (permalink / raw) To: Kuninori Morimoto; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Morimoto-san, On Thursday, 18 October 2018 05:12:14 EET Kuninori Morimoto wrote: > Hi Vladimir, Laurent > > I'm testing ULCB board, and I noticed that HDMI doen't work on it. > > - Sometimes kernel panic happen (I lost log, but it said "get crc" > something error), - Often, kernel doesn't boot with below log if I > connected HDMI cable when booting > - Monitor say "No signal" if I connected cable *after* booting > > I'm using Geert's renesas-drivers-2018-10-09-v4.19-rc7 branch. > It seems salvator HDMI is working correctly on it. > I attached my .config I tried to reproduce the problem, starting with drm-next which seems to work fine, moving to renesas-drivers-2018-10-09-v4.19-rc7 which also didn't exhibit any issue. I then used your kernel configuration, and got a WARN_ON \o/ [ 1.805110] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 1.811758] [drm] No driver support for vblank timestamp query. [ 1.878688] WARNING: CPU: 1 PID: 62 at /home/laurent/src/iob/renesas/linux/ drivers/gpu/drm/rcar-du/rcar_du_crtc.c:229 rcar_du_crtc_get+0x604/0x628 [ 1.878712] CPU: 1 PID: 62 Comm: kworker/1:1 Not tainted 4.19.0-rc7 #2820 [ 1.878716] Hardware name: Renesas H3ULCB Kingfisher board based on r8a7795 ES2.0+ (DT) [ 1.878725] Workqueue: events deferred_probe_work_func [ 1.878734] pstate: 00000005 (nzcv daif -PAN -UAO) [ 1.878739] pc : rcar_du_crtc_get+0x604/0x628 [ 1.878743] lr : rcar_du_crtc_get+0xa8/0x628 [ 1.878747] sp : ffff00000a12b330 [ 1.878750] x29: ffff00000a12b330 x28: 0000000000000000 [ 1.878759] x27: 0000000000000004 x26: ffff8006f90fc000 [ 1.878768] x25: ffff8006f9de3ad8 x24: 0000000000000001 [ 1.878776] x23: 0000000000000001 x22: 0000000006590fa0 [ 1.878784] x21: ffff8006f9026818 x20: ffff000008a6e000 [ 1.878792] x19: ffff8006f9610770 x18: 0000000000001ef4 [ 1.878799] x17: 0000000000000000 x16: ffff8006faee5900 [ 1.878807] x15: 0000000000001eeb x14: ffff0000096a9000 [ 1.878815] x13: 0000000000001ef6 x12: 0000000000001eeb [ 1.878823] x11: ffff8006faee60e0 x10: ffff000008ab5000 [ 1.878831] x9 : ffff0000098ad000 x8 : ffff8006faee5900 [ 1.878839] x7 : ffff000008b1a000 x6 : ffff000008b1a308 [ 1.878847] x5 : 0000000000000002 x4 : 0000000000000006 [ 1.878855] x3 : ffff0000087d7670 x2 : ffff8006f9610018 [ 1.878862] x1 : 0000000000000000 x0 : ffff8006f9611cf0 [ 1.878871] Call trace: [ 1.878876] rcar_du_crtc_get+0x604/0x628 [ 1.878880] rcar_du_crtc_atomic_begin+0x2c/0x60 [ 1.878890] drm_atomic_helper_commit_planes+0x84/0x218 [ 1.878895] rcar_du_atomic_commit_tail+0x38/0x70 [ 1.878900] commit_tail+0x4c/0x80 [ 1.878904] drm_atomic_helper_commit+0xfc/0x178 [ 1.878911] drm_atomic_commit+0x54/0x60 [ 1.878918] restore_fbdev_mode_atomic+0x180/0x1f0 [ 1.878922] restore_fbdev_mode+0x58/0x198 [ 1.878927] drm_fb_helper_restore_fbdev_mode_unlocked+0x80/0xd8 [ 1.878932] drm_fb_helper_set_par+0x34/0x68 [ 1.878939] fbcon_init+0x504/0x558 [ 1.878945] visual_init+0xa0/0xf0 [ 1.878950] do_bind_con_driver+0x160/0x338 [ 1.878955] do_take_over_console+0x128/0x1a8 [ 1.878959] do_fbcon_takeover+0x80/0x108 [ 1.878964] fbcon_event_notify+0x9ac/0x9d8 [ 1.878971] notifier_call_chain+0x5c/0x98 [ 1.878975] __blocking_notifier_call_chain+0x58/0xa0 [ 1.878979] blocking_notifier_call_chain+0x3c/0x50 [ 1.878983] fb_notifier_call_chain+0x30/0x40 [ 1.878987] register_framebuffer+0x288/0x330 [ 1.878992] __drm_fb_helper_initial_config_and_unlock+0x24c/0x410 [ 1.878996] drm_fb_helper_fbdev_setup+0xf0/0x210 [ 1.879000] drm_fbdev_cma_init+0xa4/0xf0 [ 1.879005] rcar_du_modeset_init+0x3b4/0x570 [ 1.879009] rcar_du_probe+0x134/0x210 [ 1.879016] platform_drv_probe+0x58/0xb8 [ 1.879020] really_probe+0x20c/0x2a0 [ 1.879024] driver_probe_device+0x60/0x108 [ 1.879028] __device_attach_driver+0x9c/0xe0 [ 1.879031] bus_for_each_drv+0x80/0xe0 [ 1.879035] __device_attach+0xf0/0x150 [ 1.879039] device_initial_probe+0x24/0x30 [ 1.879042] bus_probe_device+0xa0/0xa8 [ 1.879046] deferred_probe_work_func+0x78/0xb0 [ 1.879052] process_one_work+0x2c4/0x6c0 [ 1.879055] worker_thread+0x244/0x438 [ 1.879060] kthread+0x100/0x130 [ 1.879067] ret_from_fork+0x10/0x1c [ 1.879070] irq event stamp: 42150 [ 1.879080] hardirqs last enabled at (42149): [<ffff00000873feac>] _raw_spin_unlock_irqrestore+0x7c/0x88 [ 1.879086] hardirqs last disabled at (42150): [<ffff00000808192c>] do_debug_exception+0x17c/0x1b8 [ 1.879090] softirqs last enabled at (41936): [<ffff00000808200c>] __do_softirq+0x46c/0x51c [ 1.879097] softirqs last disabled at (41915): [<ffff0000080b0914>] irq_exit+0x12c/0x138 [ 1.879100] ---[ end trace ec07bda5b9bd7ef1 ]--- I'm now investigating it. -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: HDMI doesn't work on ULCB board 2018-11-06 14:30 ` Laurent Pinchart @ 2018-11-06 15:40 ` Laurent Pinchart 2018-11-08 0:16 ` Kuninori Morimoto 0 siblings, 1 reply; 9+ messages in thread From: Laurent Pinchart @ 2018-11-06 15:40 UTC (permalink / raw) To: Kuninori Morimoto; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Morimoto-san, On Tuesday, 6 November 2018 16:30:35 EET Laurent Pinchart wrote: > On Thursday, 18 October 2018 05:12:14 EET Kuninori Morimoto wrote: > > Hi Vladimir, Laurent > > > > I'm testing ULCB board, and I noticed that HDMI doen't work on it. > > > > - Sometimes kernel panic happen (I lost log, but it said "get crc" > > > > something error), - Often, kernel doesn't boot with below log if I > > connected HDMI cable when booting > > > > - Monitor say "No signal" if I connected cable *after* booting > > > > I'm using Geert's renesas-drivers-2018-10-09-v4.19-rc7 branch. > > It seems salvator HDMI is working correctly on it. > > I attached my .config > > I tried to reproduce the problem, starting with drm-next which seems to work > fine, moving to renesas-drivers-2018-10-09-v4.19-rc7 which also didn't > exhibit any issue. I then used your kernel configuration, and got a WARN_ON > \o/ Investigations revealed that you're missing the CONFIG_COMMON_CLK_VC5=y option in your kernel configuration. It also revealed a bug in the error handling code of the DU driver, for which I have just sent "[PATCH] drm: rcar-du: Fix external clock error checks". -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: HDMI doesn't work on ULCB board 2018-11-06 15:40 ` Laurent Pinchart @ 2018-11-08 0:16 ` Kuninori Morimoto 2018-11-09 2:23 ` Kuninori Morimoto 0 siblings, 1 reply; 9+ messages in thread From: Kuninori Morimoto @ 2018-11-08 0:16 UTC (permalink / raw) To: Laurent Pinchart; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Laurent Thank you for your help > > I tried to reproduce the problem, starting with drm-next which seems to work > > fine, moving to renesas-drivers-2018-10-09-v4.19-rc7 which also didn't > > exhibit any issue. I then used your kernel configuration, and got a WARN_ON > > \o/ > > Investigations revealed that you're missing the CONFIG_COMMON_CLK_VC5=y option > in your kernel configuration. It also revealed a bug in the error handling > code of the DU driver, for which I have just sent "[PATCH] drm: rcar-du: Fix > external clock error checks". Thanks !! I tried your posted patch, and it solved Oops issue, and CONFIG_COMMON_CLK_VC5 solved HDMI outputs !! Best regards --- Kuninori Morimoto ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: HDMI doesn't work on ULCB board 2018-11-08 0:16 ` Kuninori Morimoto @ 2018-11-09 2:23 ` Kuninori Morimoto 2018-11-10 8:51 ` Laurent Pinchart 0 siblings, 1 reply; 9+ messages in thread From: Kuninori Morimoto @ 2018-11-09 2:23 UTC (permalink / raw) To: Laurent Pinchart; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Laurent > > > I tried to reproduce the problem, starting with drm-next which seems to work > > > fine, moving to renesas-drivers-2018-10-09-v4.19-rc7 which also didn't > > > exhibit any issue. I then used your kernel configuration, and got a WARN_ON > > > \o/ > > > > Investigations revealed that you're missing the CONFIG_COMMON_CLK_VC5=y option > > in your kernel configuration. It also revealed a bug in the error handling > > code of the DU driver, for which I have just sent "[PATCH] drm: rcar-du: Fix > > external clock error checks". > > Thanks !! > I tried your posted patch, and it solved Oops issue, > and CONFIG_COMMON_CLK_VC5 solved HDMI outputs !! Hmm... I noticed Salvator can't boot if .config has CONFIG_COMMON_CLK_VC5. This means, Salvator and ULCB can't use same binary so far for me (= all modules are =y on .config). I'm using previous attached .config + your patch + CONFIG_COMMON_CLK_VC5 Kernel will stop here on Salvator ----------------- .... rcar-fcp fe9af000.fcp: ignoring dependency for device, assuming no driver rcar-fcp fe9bf000.fcp: ignoring dependency for device, assuming no driver rcar-fcp fea27000.fcp: ignoring dependency for device, assuming no driver rcar-fcp fea2f000.fcp: ignoring dependency for device, assuming no driver rcar-fcp fea37000.fcp: ignoring dependency for device, assuming no driver [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] No driver support for vblank timestamp query. ** stop here ** Best regards --- Kuninori Morimoto ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: HDMI doesn't work on ULCB board 2018-11-09 2:23 ` Kuninori Morimoto @ 2018-11-10 8:51 ` Laurent Pinchart 2018-11-12 3:09 ` Kuninori Morimoto 0 siblings, 1 reply; 9+ messages in thread From: Laurent Pinchart @ 2018-11-10 8:51 UTC (permalink / raw) To: Kuninori Morimoto; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Morimoto-san, On Friday, 9 November 2018 04:23:36 EET Kuninori Morimoto wrote: > Hi Laurent > > >>> I tried to reproduce the problem, starting with drm-next which seems > >>> to work fine, moving to renesas-drivers-2018-10-09-v4.19-rc7 which > >>> also didn't exhibit any issue. I then used your kernel configuration, > >>> and got a WARN_ON \o/ > >> > >> Investigations revealed that you're missing the CONFIG_COMMON_CLK_VC5=y > >> option in your kernel configuration. It also revealed a bug in the > >> error handling code of the DU driver, for which I have just sent > >> "[PATCH] drm: rcar-du: Fix external clock error checks". > > > > Thanks !! > > I tried your posted patch, and it solved Oops issue, > > and CONFIG_COMMON_CLK_VC5 solved HDMI outputs !! > > Hmm... > > I noticed Salvator can't boot if .config has CONFIG_COMMON_CLK_VC5. > This means, Salvator and ULCB can't use same binary so far for me > (= all modules are =y on .config). > I'm using previous attached .config + your patch + CONFIG_COMMON_CLK_VC5 > > Kernel will stop here on Salvator > > ----------------- > .... > rcar-fcp fe9af000.fcp: ignoring dependency for device, assuming no driver > rcar-fcp fe9bf000.fcp: ignoring dependency for device, assuming no driver > rcar-fcp fea27000.fcp: ignoring dependency for device, assuming no driver > rcar-fcp fea2f000.fcp: ignoring dependency for device, assuming no driver > rcar-fcp fea37000.fcp: ignoring dependency for device, assuming no driver > [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [drm] No driver support for vblank timestamp query. > > ** stop here ** I'm afraid I can't reproduce this. I checked out renesas-drivers-2018-10-09- v4.19-rc7, applied the fix I've submitted, took your configuration, enabled CONFIG_COMMON_CLK_VC5, and my Salvator-XS H3 boots fine. -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: HDMI doesn't work on ULCB board 2018-11-10 8:51 ` Laurent Pinchart @ 2018-11-12 3:09 ` Kuninori Morimoto 2018-11-12 3:23 ` Laurent Pinchart 0 siblings, 1 reply; 9+ messages in thread From: Kuninori Morimoto @ 2018-11-12 3:09 UTC (permalink / raw) To: Laurent Pinchart; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Laurent > > I noticed Salvator can't boot if .config has CONFIG_COMMON_CLK_VC5. > > This means, Salvator and ULCB can't use same binary so far for me > > (= all modules are =y on .config). > > I'm using previous attached .config + your patch + CONFIG_COMMON_CLK_VC5 (snip) > I'm afraid I can't reproduce this. I checked out renesas-drivers-2018-10-09- > v4.19-rc7, applied the fix I've submitted, took your configuration, enabled > CONFIG_COMMON_CLK_VC5, and my Salvator-XS H3 boots fine. I'm deeply sorry, it was my fault. I'm using ES1.x board, but I used XS dtb Best regards --- Kuninori Morimoto ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: HDMI doesn't work on ULCB board 2018-11-12 3:09 ` Kuninori Morimoto @ 2018-11-12 3:23 ` Laurent Pinchart 0 siblings, 0 replies; 9+ messages in thread From: Laurent Pinchart @ 2018-11-12 3:23 UTC (permalink / raw) To: Kuninori Morimoto; +Cc: Simon, Vladimir Barinov, Magnus, Linux-Renesas Hi Morimoto-san, On Monday, 12 November 2018 05:09:13 EET Kuninori Morimoto wrote: > Hi Laurent > > >> I noticed Salvator can't boot if .config has CONFIG_COMMON_CLK_VC5. > >> This means, Salvator and ULCB can't use same binary so far for me > >> (= all modules are =y on .config). > >> I'm using previous attached .config + your patch + CONFIG_COMMON_CLK_VC5 > > (snip) > > > I'm afraid I can't reproduce this. I checked out > > renesas-drivers-2018-10-09- v4.19-rc7, applied the fix I've submitted, > > took your configuration, enabled CONFIG_COMMON_CLK_VC5, and my > > Salvator-XS H3 boots fine. > > I'm deeply sorry, it was my fault. > I'm using ES1.x board, but I used XS dtb I've done worse mistakes, and many times, so I can't blame you :-) I'm glad it works now. -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2018-11-12 13:14 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <87bm7svwmp.wl-kuninori.morimoto.gx@renesas.com> 2018-10-19 13:32 ` HDMI doesn't work on ULCB board Laurent Pinchart 2018-10-29 1:07 ` Kuninori Morimoto 2018-11-06 14:30 ` Laurent Pinchart 2018-11-06 15:40 ` Laurent Pinchart 2018-11-08 0:16 ` Kuninori Morimoto 2018-11-09 2:23 ` Kuninori Morimoto 2018-11-10 8:51 ` Laurent Pinchart 2018-11-12 3:09 ` Kuninori Morimoto 2018-11-12 3:23 ` Laurent Pinchart
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.