All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: anton.antonov@arm.com
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH v3 2/2] trusted-service: remove optee udev and group settings
Date: Fri, 18 Oct 2024 08:51:57 +0300	[thread overview]
Message-ID: <ZxH3fUZB1Q1ozwSP@nuoska> (raw)
In-Reply-To: <18350.1729176507648104860@lists.yoctoproject.org>

Hi,

On Thu, Oct 17, 2024 at 07:48:27AM -0700, Anton Antonov via lists.yoctoproject.org wrote:
> On Thu, Oct 17, 2024 at 04:09 AM, Mikko Rapeli wrote:
> 
> > 
> > I'm still not sure of the right direction. Which recipes and layers have
> > userspace
> > SW which needs to access /dev/tee* or /dev/teepriv* devices nodes without
> > root
> > rights in userspace? Where is a test for these recipes or functionality?
> 
> Parsec is the example you're looking for. And parsec oeqa tests would test TS provider if included

Thanks! So meta-security/recipes-parsec/parsec-service/parsec-service_1.4.1.bb
would need to change from "teeclnt" to "tee" group to access /dev/tee* devices
according to optee-client udev rule. I can provide the change when/if this
series gets merged. Same for meta-cassini.

But does the really need to be a separate copy of the optee-client udev rule
for TS setups which need optee but not tee-supplicant from optee-client binary
package?

Cheers,

-Mikko


  reply	other threads:[~2024-10-18  5:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  6:59 [PATCH v3 1/2] optee-client: use udev rule and systemd service from upstream Mikko Rapeli
2024-10-17  6:59 ` [PATCH v3 2/2] trusted-service: remove optee udev and group settings Mikko Rapeli
2024-10-17  8:17   ` [meta-arm] " Gyorgy Szing
2024-10-17  8:34     ` Mikko Rapeli
2024-10-17  9:44       ` Gyorgy Szing
2024-10-17  9:52         ` Mikko Rapeli
2024-10-17 10:54           ` Gyorgy Szing
2024-10-17 11:09             ` Mikko Rapeli
2024-10-17 13:38               ` Gyorgy Szing
2024-10-17 13:38               ` Adam Johnston
2024-10-17 14:48               ` Anton Antonov
2024-10-18  5:51                 ` Mikko Rapeli [this message]
2024-10-23 14:22 ` [PATCH v3 1/2] optee-client: use udev rule and systemd service from upstream Tom Hochstein (OSS)
2024-10-23 14:30   ` Mikko Rapeli
     [not found]     ` <PAXPR04MB9448DC39953E357F3E73D07EE24D2@PAXPR04MB9448.eurprd04.prod.outlook.com>
2024-10-23 14:54       ` Mikko Rapeli
2024-10-29 17:02         ` Tom Hochstein
2024-10-30  8:02           ` [meta-arm] " Gyorgy Szing
2024-11-26 14:55             ` Mikko Rapeli
2024-11-26 21:05               ` Gyorgy Szing
2024-11-27 14:27                 ` Mikko Rapeli
2024-12-11 14:42               ` Ross Burton

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=ZxH3fUZB1Q1ozwSP@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=anton.antonov@arm.com \
    --cc=meta-arm@lists.yoctoproject.org \
    /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.