From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: Frieder Schrempf <frieder.schrempf@kontron.de>
Cc: Jagan Teki <jagan@amarulasolutions.com>, dri-devel@lists.freedesktop.org
Subject: Re: IMX8MM: assign panel to mipi_dsi in a device tree
Date: Mon, 6 Mar 2023 19:05:58 +0000 [thread overview]
Message-ID: <20230306200558.5b40fa44@yaise-pc1> (raw)
In-Reply-To: <50f7516d-0057-8c8e-654c-f9b1b4176588@kontron.de>
On Mon, 6 Mar 2023 09:43:22 +0100
Frieder Schrempf <frieder.schrempf@kontron.de> wrote:
>This is the NXP vendor kernel which differs a lot from mainline,
>especially in the graphics/display area. You probably won't get much
>support from this list as most people here (including me) would advise
>against using the vendor kernel at all.
Understandable, I did the same at the time when I was working in media
and DVB was still a thing.
>Probably they are working and probably you can get your setup working,
>too, somehow. But you would need to ask for help in the NXP community
>or elsewhere. The other option is to switch to mainline (recommended)
>and use Jagan's patches for DSIM support that are about to be
>upstreamed.
Thanks for your feedback. Unfortunately my client wants to stick with
the vendor kernel, so my only chance is to see whether it works with
upstream mainline and if so, at least I know the hardware is OK.
Why oh why do we have vendor kernels? In small-system's Linux there
sooo many vendor kernels. Very hard to understand. It's 2023.
The answers to a similar problem I found in the NXP community board
was: go look at the driver source and see what's wrong.
Thanks again for your answers.
best regards,
--
Patrick.
prev parent reply other threads:[~2023-03-06 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 15:22 IMX8MM: assign panel to mipi_dsi in a device tree Patrick Boettcher
2023-03-05 18:35 ` Jagan Teki
2023-03-05 19:45 ` Patrick Boettcher
2023-03-06 8:43 ` Frieder Schrempf
2023-03-06 19:05 ` Patrick Boettcher [this message]
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=20230306200558.5b40fa44@yaise-pc1 \
--to=patrick.boettcher@posteo.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=frieder.schrempf@kontron.de \
--cc=jagan@amarulasolutions.com \
/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 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.