All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Paul Elder <paul.elder@ideasonboard.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/2] package/kmsxx: Add support for pykms
Date: Fri, 2 Oct 2026 22:37:09 +0300	[thread overview]
Message-ID: <20261002193709.GC91932@killaraus.ideasonboard.com> (raw)
In-Reply-To: <f27d7de1-d26a-47a6-bf33-074277c44d73@ideasonboard.com>

On Fri, Oct 02, 2026 at 04:05:29PM +0300, Tomi Valkeinen wrote:
> On 02/10/2026 13:23, Paul Elder wrote:
> > This series adds support for pykms in kmsxx. This enables the python
> > bindings for kmsxx.
> > 
> > The first patch updates kmsxx to the current HEAD, and the second patch
> > adds support for pykms as a separate build config option.
> 
> I don't recall the exact problems, but pybind11 was difficult... Or was 
> it about installing the module to the right place. But if it works now, 
> good =).

The issue with the current buildroot package is that the version of
kmsxx compiled and linked fine, but pykms.so contained unresolved symbol
when the meson utils option was disabled. You have fixed that, so we
decided to just bump the version as an easy fix.

> However, I have not used kms++'s python bindings for a long time, and 
> consider them deprecated. Have you tried https://github.com/tomba/pykms?

Paul's paul to enable the kmsxx Python bindings come from their usage in
kms-tests (https://git.ideasonboard.com/renesas/kms-tests). If pykms
gets packaged in buildroot we could consider it. For the time being, is
there any drawback in enabling the kmsxx Python bindings ?

-- 
Regards,

Laurent Pinchart
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-10-02 19:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 10:23 [Buildroot] [PATCH 0/2] package/kmsxx: Add support for pykms Paul Elder
2026-10-02 10:23 ` [Buildroot] [PATCH 1/2] package/kmsxx: Bump version to current head as of 2026.10 Paul Elder
2026-10-02 12:51   ` Laurent Pinchart
2026-10-02 19:27   ` Thomas Petazzoni via buildroot
2026-10-02 10:23 ` [Buildroot] [PATCH 2/2] package/kmsxx: Add option for pykms Paul Elder
2026-10-02 12:53   ` Laurent Pinchart
2026-10-02 19:28   ` Thomas Petazzoni via buildroot
     [not found] ` <f27d7de1-d26a-47a6-bf33-074277c44d73@ideasonboard.com>
2026-10-02 19:37   ` Laurent Pinchart [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=20261002193709.GC91932@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=buildroot@buildroot.org \
    --cc=paul.elder@ideasonboard.com \
    --cc=tomi.valkeinen@ideasonboard.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.