From: Marco Felsch <m.felsch@pengutronix.de>
To: ptxdist@pengutronix.de, Matthias Fend <matthias.fend@emfend.at>
Subject: Re: [ptxdist] [PATCH v2 1/1] libcamera: new package
Date: Wed, 14 Sep 2022 10:03:09 +0200 [thread overview]
Message-ID: <20220914080309.swx7w4l4yrwspuj6@pengutronix.de> (raw)
In-Reply-To: <20220913153140.GB28082@pengutronix.de>
On 22-09-13, Michael Olbrich wrote:
> On Tue, Sep 13, 2022 at 03:53:21PM +0200, Marco Felsch wrote:
> > Hi Matthias,
...
> > > + select QT5 if LIBCAMERA_QCAM
> > > + select QT5_MODULE_QTBASE if LIBCAMERA_QCAM
> > > + select QT5_MODULE_QTBASE_GUI if LIBCAMERA_QCAM
> > > + select QT5_MODULE_QTBASE_WIDGETS if LIBCAMERA_QCAM
> > > + help
> > > + A complex camera support library for Linux, Android, and ChromeOS.
> > > +
> > > +if LIBCAMERA
> >
> > I would provide the user the choice of selecting/enabling the ipa module
> > signing.
>
> Hmmm, what would be the benefit of making this optional?
To leave the user the option to not enable it at all. Maybe your rootfs
size is very limited and you can't pull any of crpytolibs, then you can
turn it off.
> And if the modules are not signed then they should be stripped.
The IPAs running in a seperate process if they are not signed. So the
user has the choice between runtime overhead <-> rootfs size.
Regards,
Marco
next prev parent reply other threads:[~2022-09-14 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 10:41 [ptxdist] [PATCH v2 0/1] " Matthias Fend
2022-09-11 10:41 ` [ptxdist] [PATCH v2 1/1] " Matthias Fend
2022-09-13 13:53 ` Marco Felsch
2022-09-13 15:31 ` Michael Olbrich
2022-09-14 8:03 ` Marco Felsch [this message]
2022-09-14 6:04 ` Matthias Fend
2022-09-14 7:50 ` Marco Felsch
2022-09-14 13:06 ` Michael Olbrich
2022-09-13 15:24 ` Michael Olbrich
2022-09-14 5:54 ` Matthias Fend
2022-09-14 12:59 ` Michael Olbrich
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=20220914080309.swx7w4l4yrwspuj6@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=matthias.fend@emfend.at \
--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