From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/modem-manager: bump version to 1.16.2
Date: Mon, 29 Mar 2021 21:42:40 +0200 [thread overview]
Message-ID: <YGItsBIZ32zztrcg@pevik> (raw)
In-Reply-To: <CAAP7uc+KkOsiPYvu=ac43X9nno-7LJw2DEtSExLETXR_VN+jXw@mail.gmail.com>
> > RFC: should I add also --enable-plugin-qcom-soc ?
> > (there is qcom-db410c-firmware package)
> The qcom-soc plugin is only relevant if the system where you're running the
> system is a Qualcomm SoC, and if you woulf plan to use the builtin modem as
> a modem in ModemManager. An obvious use case is e.g. qualcomm-phones
> running postmarketos.
Yep, in postmarketOS it does make perfect sense.
> For any other kind of setup, where MM is supposed to use external (e.g.
> USB, serial...) modems, the qcom-soc plugin is not needed. But it really
> wouldn't harm to have it either, it would just waste space (in the same way
> as other plugins that may never be used really).
> Maybe enable it? I should have probably done that in upstream really, as it
> doesn't really collide with other stuff
Maybe having an option for user to decide? Most of the people won't need it,
but it'd be nice to leave it for Dragonboard 410c (not sure if it uses modem).
Kind regards,
Petr
next prev parent reply other threads:[~2021-03-29 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 18:49 [Buildroot] [PATCH 1/1] package/modem-manager: bump version to 1.16.2 Petr Vorel
2021-03-29 19:28 ` Aleksander Morgado
2021-03-29 19:42 ` Petr Vorel [this message]
2021-03-29 19:59 ` Aleksander Morgado
2021-03-30 19:51 ` Yann E. MORIN
2021-03-30 19:58 ` Aleksander Morgado
2021-03-30 20:09 ` Petr Vorel
2021-03-31 18:24 ` Petr Vorel
2021-03-31 19:12 ` Aleksander Morgado
2021-04-02 5:05 ` Petr Vorel
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=YGItsBIZ32zztrcg@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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