Re: [PATCH] of: Preserve "of-display" device name for compatibility

2023-07-10 Thread Michal Suchánek
gt; Cc: Cyril Brulebois > Cc: Thomas Zimmermann > Cc: Helge Deller > Signed-off-by: Rob Herring This is exclusive with the other patchset that updates the other side: https://lore.kernel.org/lkml/20230412095509.2196162-1-cy...@debamax.com/ Reviewed-by: Michal Suchánek Thanks Michal > ---

Re: [PATCH 2/2] drm/ofdrm: Update expected device name

2023-07-10 Thread Michal Suchánek
ps://bugs.debian.org/1033058 > Fixes: 241d2fb56a18 ("of: Make OF framebuffer device names unique") > Cc: sta...@vger.kernel.org # v6.2+ > Signed-off-by: Cyril Brulebois Reviewed-by: Michal Suchánek > --- > drivers/gpu/drm/tiny/ofdrm.c | 2 +- > 1 file changed, 1 insertion(+

Re: [PATCH 1/2] fbdev/offb: Update expected device name

2023-07-10 Thread Michal Suchánek
ot;of: Make OF framebuffer device names unique") > Cc: sta...@vger.kernel.org > Signed-off-by: Cyril Brulebois Reviewed-by: Michal Suchánek Thanks Michal > --- > drivers/video/fbdev/offb.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/driv

Re: [PATCH 1/2] fbdev/offb: Update expected device name

2023-06-20 Thread Michal Suchánek
On Tue, Jun 20, 2023 at 08:24:34AM +0200, Helge Deller wrote: > On 6/15/23 23:19, Cyril Brulebois wrote: > > Hi Rob, > > > > Rob Herring (2023-06-15): > > > On Thu, Jun 15, 2023 at 03:21:07PM +0200, Michal Suchánek wrote: > > > > At the time this

Re: [PATCH 1/2] fbdev/offb: Update expected device name

2023-06-15 Thread Michal Suchánek
Hello, On Thu, Jun 15, 2023 at 03:06:28PM +0200, Thomas Zimmermann wrote: > Hi > > Am 15.06.23 um 15:03 schrieb Linux regression tracking (Thorsten Leemhuis): > > On 16.04.23 14:34, Salvatore Bonaccorso wrote: > > > > > > On Wed, Apr 12, 2023 at 11:55:08AM +0200, Cyril Brulebois wrote: > > > >

Re: [PATCH 2/2] drm/ofdrm: Update expected device name

2023-05-22 Thread Michal Suchánek
On Mon, Apr 24, 2023 at 11:07:45AM +0200, Thomas Zimmermann wrote: > Hi > > Am 24.04.23 um 09:33 schrieb Geert Uytterhoeven: > > Hi Cyril, > > > > CC DT > > > > On Wed, Apr 12, 2023 at 12:05 PM Cyril Brulebois wrote: > > > Since commit 241d2fb56a18 ("of: Make OF framebuffer device names

Re: [PATCH -next] fbdev: offb: allow build when DRM_OFDRM=m

2022-11-23 Thread Michal Suchánek
of =m. > > > > Fixes: c8a17756c425 ("drm/ofdrm: Add ofdrm for Open Firmware framebuffers") > > Signed-off-by: Randy Dunlap > > Suggested-by: Masahiro Yamada > > Cc: Thomas Zimmermann > > Cc: Michal Suchánek > > Cc: linuxppc-...@lists.ozlabs.or

Re: [PATCH v5 1/5] drm/ofdrm: Add ofdrm for Open Firmware framebuffers

2022-11-19 Thread Michal Suchánek
Hello, On Tue, Oct 11, 2022 at 05:07:08PM +0200, Thomas Zimmermann wrote: > Open Firmware provides basic display output via the 'display' node. > DT platform code already provides a device that represents the node's > framebuffer. Add a DRM driver for the device. The display mode and > color

Re: [PATCH v4 5/5] drm/ofdrm: Support big-endian scanout buffers

2022-10-12 Thread Michal Suchánek
On Wed, Oct 12, 2022 at 05:59:45PM +0300, Ville Syrjälä wrote: > On Wed, Oct 12, 2022 at 04:31:14PM +0200, Thomas Zimmermann wrote: > > Hi > > > > Am 12.10.22 um 15:12 schrieb Arnd Bergmann: > > > On Wed, Oct 12, 2022, at 2:00 PM, Thomas Zimmermann wrote: > > >> > > >> Could well be. But ofdrm

Re: [PATCH v4 5/5] drm/ofdrm: Support big-endian scanout buffers

2022-10-12 Thread Michal Suchánek
Hello, On Wed, Oct 12, 2022 at 03:12:35PM +0200, Arnd Bergmann wrote: > On Wed, Oct 12, 2022, at 2:00 PM, Thomas Zimmermann wrote: > > > > Could well be. But ofdrm intents to replace offb and this test has > > worked well in offb for almost 15 yrs. If there are bug reports, I'm > > happy to

Re: [PATCH v4 5/5] drm/ofdrm: Support big-endian scanout buffers

2022-10-12 Thread Michal Suchánek
On Wed, Oct 12, 2022 at 10:38:29AM +0200, Arnd Bergmann wrote: > On Wed, Oct 12, 2022, at 10:27 AM, Thomas Zimmermann wrote: > > Am 12.10.22 um 09:44 schrieb Arnd Bergmann: > >> On Wed, Oct 12, 2022, at 9:40 AM, Thomas Zimmermann wrote: > >>> Am 12.10.22 um 09:17 schrieb Arnd Bergmann: > On

Re: [PATCH v4 5/5] drm/ofdrm: Support big-endian scanout buffers

2022-10-11 Thread Michal Suchánek
On Tue, Oct 11, 2022 at 10:06:59PM +0200, Arnd Bergmann wrote: > On Tue, Oct 11, 2022, at 1:30 PM, Thomas Zimmermann wrote: > > Am 11.10.22 um 09:46 schrieb Javier Martinez Canillas: > >>> +static bool display_get_big_endian_of(struct drm_device *dev, struct > >>> device_node *of_node) > >>> +{ >

Re: [PATCH v4 5/5] drm/ofdrm: Support big-endian scanout buffers

2022-09-28 Thread Michal Suchánek
Hello, On Wed, Sep 28, 2022 at 12:50:10PM +0200, Thomas Zimmermann wrote: > All DRM formats assume little-endian byte order. On big-endian systems, > it is likely that the scanout buffer is in big endian as well. Update > the format accordingly and add endianess conversion to the format-helper >

Re: [PATCH v2 00/10] drm: Add driver for PowerPC OF displays

2022-07-28 Thread Michal Suchánek
Hello, On Thu, Jul 28, 2022 at 09:13:59PM +1000, Michael Ellerman wrote: > Thomas Zimmermann writes: > > (was: drm: Add driverof PowerPC OF displays) > > > > PowerPC's Open Firmware offers a simple display buffer for graphics > > output. Add ofdrm, a DRM driver for the device. As with the

Re: [PATCH v2 09/10] drm/ofdrm: Add per-model device function

2022-07-26 Thread Michal Suchánek
Hello, On Tue, Jul 26, 2022 at 03:38:37PM +0200, Javier Martinez Canillas wrote: > On 7/20/22 16:27, Thomas Zimmermann wrote: > > Add a per-model device-function structure in preparation of adding > > color-management support. Detection of the individual models has been > > taken from fbdev's

Re: [PATCH 2/2] drm/tiny: Add ofdrm for Open Firmware framebuffers

2022-05-19 Thread Michal Suchánek
On Wed, May 18, 2022 at 10:11:03PM +0100, Mark Cave-Ayland wrote: > On 18/05/2022 19:30, Thomas Zimmermann wrote: > > > Open Firmware provides basic display output via the 'display' node. > > DT platform code already provides a device that represents the node's > > framebuffer. Add a DRM driver

Re: [PATCH 2/2] drm/tiny: Add ofdrm for Open Firmware framebuffers

2022-05-18 Thread Michal Suchánek
Hello, On Wed, May 18, 2022 at 08:30:06PM +0200, Thomas Zimmermann wrote: > Open Firmware provides basic display output via the 'display' node. > DT platform code already provides a device that represents the node's > framebuffer. Add a DRM driver for the device. The display mode and > color

Re: [PATCH] simpldrm: Enable boot time VESA graphic mode selection.

2022-03-02 Thread Michal Suchánek
Hello, On Wed, Mar 02, 2022 at 08:31:25PM +0100, Thomas Zimmermann wrote: > Hi, > > is this ready to be merged? The objections raised so far have been addressed in v4. I think this is good to merge. Thanks Michal > > Best regards > Thomas > > Am 18.02.22 um 10:33 schrieb Michal Suchanek:

Re: [PATCH v3] simplefb: Enable boot time VESA graphic mode selection.

2022-02-23 Thread Michal Suchánek
On Wed, Feb 23, 2022 at 07:34:54PM +0100, Javier Martinez Canillas wrote: > On 2/23/22 19:23, Michal Suchánek wrote: > > [snip] > > >> My point about the subject line remains thought, I would use something > >> like: > >> > >> firmware: sys

Re: [PATCH v3] simplefb: Enable boot time VESA graphic mode selection.

2022-02-23 Thread Michal Suchánek
On Wed, Feb 23, 2022 at 07:13:07PM +0100, Javier Martinez Canillas wrote: > On 2/23/22 18:12, Michal Suchánek wrote: > > On Wed, Feb 23, 2022 at 05:54:54PM +0100, Javier Martinez Canillas wrote: > > [snip] > > >> > >> Yes, that's what I tried to say. But

Re: [PATCH v3] simplefb: Enable boot time VESA graphic mode selection.

2022-02-23 Thread Michal Suchánek
On Wed, Feb 23, 2022 at 05:54:54PM +0100, Javier Martinez Canillas wrote: > On 2/23/22 17:45, Michal Suchánek wrote: > > [snip] > > >>> > >>> To enable use of VESA modes with simplefb in legacy BIOS boot mode drop > >> > >> I think you meant

Re: [PATCH v3] simplefb: Enable boot time VESA graphic mode selection.

2022-02-23 Thread Michal Suchánek
On Wed, Feb 23, 2022 at 05:34:50PM +0100, Javier Martinez Canillas wrote: > Hello Michal, > > On 2/18/22 17:04, Michal Suchanek wrote: > > Since switch to simplefb/simpledrm VESA graphic modes are no longer > > available with legacy BIOS. > > Maybe you can mention that is the "vga=" kernel

Re: [PATCH v2] simplefb: Enable boot time VESA graphic mode selection.

2022-02-18 Thread Michal Suchánek
On Fri, Feb 18, 2022 at 12:36:10PM +0100, Thomas Zimmermann wrote: > Hi > > Am 18.02.22 um 11:51 schrieb Michal Suchanek: > > Since switch to simplefb/simpledrm VESA graphic modes are no longer > > available with legacy BIOS. > > > > The x86 realmode boot code enables the VESA graphic modes when

Re: [PATCH] simpldrm: Enable boot time VESA graphic mode selection.

2022-02-18 Thread Michal Suchánek
Hello, On Fri, Feb 18, 2022 at 10:57:33AM +0100, Thomas Zimmermann wrote: > Hi Michal > > Am 18.02.22 um 10:33 schrieb Michal Suchanek: > > Since switch to simpledrm VESA graphic modes are no longer available > > with legacy BIOS. > > > > The x86 realmode boot code enables the VESA graphic

Re: [PATCH] drm/bridge: fix LONTIUM_LT8912B dependencies

2021-05-05 Thread Michal Suchánek
On Wed, May 05, 2021 at 12:02:07AM +0200, Adrien Grassein wrote: > LONTIUM_LT8912B uses "drm_display_mode_to_videomode" from > DRM framework that needs VIDEOMODE_HELPERS to be enabled. > > Fixes: 30e2ae943c26 ("drm/bridge: Introduce LT8912B DSI to HDMI bridge"

ERROR: modpost: "drm_display_mode_to_videomode" [drivers/gpu/drm/bridge/lontium-lt8912b.ko] undefined!

2021-05-04 Thread Michal Suchánek
Hello, I get errors about missing symbol in the lontium-lt8912b module. Is the problem self-evident or do you need the config as well? I don't need the driver for anything, it was just auto-enabled because it's new and the change has not been reviewed. Thanks Michal > > Last output: > WRAP