All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Sapp <rs@ti.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Andrew Davis <afd@ti.com>, Ryan Eatmon <reatmon@ti.com>,
	<meta-arago@lists.yoctoproject.org>
Subject: Re: [EXTERNAL] Re: [DISCUSSION] Weston-Init and non-root weston
Date: Tue, 18 Apr 2023 21:30:29 -0500	[thread overview]
Message-ID: <c0a547bd-bf97-a58c-3c60-e1530731325f@ti.com> (raw)
In-Reply-To: <20230418225101.GY9226@denix.org>

On 4/18/23 17:51, Denys Dmytriyenko wrote:
> On Mon, Apr 17, 2023 at 06:16:19PM -0500, Randolph Sapp wrote:
>> On 4/17/23 18:08, Andrew Davis wrote:
>>> On 4/17/23 6:01 PM, Randolph Sapp wrote:
>>>> On 4/17/23 17:52, Andrew Davis wrote:
>>>>> On 4/17/23 5:43 PM, Randolph Sapp wrote:
>>>>>> On 4/17/23 17:39, Andrew Davis wrote:
>>>>>>> On 4/17/23 5:32 PM, Randolph Sapp wrote:
>>>>>>>> Finally getting around to weston-init issue I
>>>>>>>> highlighted a while back and there's only one real issue
>>>>>>>> preventing us from reusing the base weston-init recipe
>>>>>>>> -- our touchscreen auto-configuration script.
>>>>>>>>
>>>>>>>> That script has to have root access to setup and reload
>>>>>>>> udev rules and as we know setuid won't work for shell
>>>>>>>> scripts.
>>>>>>>>
>>>>>>>> I propose we rewrite it in something that can use setuid
>>>>>>>> (perl or c or something of the sort). I'm currently
>>>>>>>> looking at perl as there's already quite a few core
>>>>>>>> recipes that rdepend on it.
>>>>>>>>
>>>>>>>> Then we just need to inject it into the runWeston script
>>>>>>>> and adjust the two init scripts to point at that.
>>>>>>>>
>>>>>>>> Any concerns or objections?
>>>>>>>
>>>>>>> Why not just drop out that old touchscreen script, it is a
>>>>>>> non-standard way of doing
>>>>>>> this task and should be removed.
>>>>>>>
>>>>>>> Andrew
>>>>>>
>>>>>> It's non-standard, but that's because there really isn't a
>>>>>> good standard for calibrating touch screens under Weston.
>>>>>> AFAIK this is still useful.
>>>>>
>>>>> https://wiki.st.com/stm32mpu/wiki/How_to_calibrate_the_touchscreen
>>>>>
>>>>> This seems like the standard ^^
>>>>>
>>>>> Andrew
>>>>
>>>> That does save the config for the user running weston. Currently
>>>> our script saves and loads the config for all users. This could
>>>> technically be seen as a regression, but it doesn't seem that
>>>> bad to me.

Whoops, that does not save the config for the user, it just applies it 
for the session. We'll still need a script to launch the calibrator on 
detection of a touch screen, and a helper script to hook into the 
calibration_helper [1].

[1] https://man.archlinux.org/man/weston.ini.5.html#calibration_helper=


      reply	other threads:[~2023-04-19  2:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 22:32 [DISCUSSION] Weston-Init and non-root weston Randolph Sapp
2023-04-17 22:39 ` Andrew Davis
2023-04-17 22:43   ` Randolph Sapp
2023-04-17 22:52     ` Andrew Davis
2023-04-17 23:01       ` Randolph Sapp
2023-04-17 23:08         ` Andrew Davis
2023-04-17 23:16           ` Randolph Sapp
2023-04-18 22:51             ` Denys Dmytriyenko
2023-04-19  2:30               ` Randolph Sapp [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=c0a547bd-bf97-a58c-3c60-e1530731325f@ti.com \
    --to=rs@ti.com \
    --cc=afd@ti.com \
    --cc=denis@denix.org \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.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.