From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] mesalib 2021.11 broken kmsro driver?
Date: Mon, 8 Nov 2021 14:03:04 +0100 [thread overview]
Message-ID: <20211108130304.GL22301@pengutronix.de> (raw)
In-Reply-To: <b0b1b5d5-aa24-113e-9940-ad67d13d017e@t2data.com>
Hi,
On Mon, Nov 08, 2021 at 11:16:11AM +0100, Christian Melki wrote:
> The kmsro driver doesn't seem to create any .so files.
> According to people on #dri-devel it's builtin in other .so files?
> So the idea of kmsro library names to copy will fail in the current .make.
What exactly is broken? In general, all gallium drivers are built into a
single file. 'make install' creates hardlinks for all drivers that are
built. In ptxdist we just create one gallium_dri.so and symlinks for all
drivers.
The 'kmsro' argument for the meson 'gallium-drivers' options just means,
build all KMS only drivers. So the list of hardlinks/softlinks ist
different. That's why we have the '$(subst kmsro, ....'.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-11-08 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 10:16 Christian Melki
2021-11-08 13:03 ` Michael Olbrich [this message]
2021-11-08 13:37 ` Christian Melki
2021-11-08 14:08 ` Lucas Stach
2021-11-08 14:28 ` Christian Melki
2021-11-09 15:42 ` Michael Olbrich
2021-11-09 15:46 ` Christian Melki
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=20211108130304.GL22301@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox