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: Wed, 31 Mar 2021 20:24:48 +0200 [thread overview]
Message-ID: <YGS+cAr0P67MDjFa@pevik> (raw)
In-Reply-To: <CAAP7ucJbn39MmCDtJkTj57cnv8F9QzG=M9SyNcnkWtZ_Ch0uSg@mail.gmail.com>
Hi Aleksander,
> > > RFC: should I add also --enable-plugin-qcom-soc ?
> > > (there is qcom-db410c-firmware package)
> > Maybe you could enable the plugin if the package is enabled:
> > ifeq ($(BR2_PACKAGE_QCOM_DB410_FIRMWARE),y)
> > MODEM_MANAGER_CONF_OPTS += --enable-plugin-qcom-soc
> > else
> > MODEM_MANAGER_CONF_OPTS += --disable-plugin-qcom-soc
> > endif
> From a quick Google search, looks like there is no WWAN modem there:
> "The DragonBoard 410c based on Qualcomm Snapdragon 410 processor is a
> 64-bit development board with Wi-Fi, Bluetooth, and GPS."
> The qcom-soc plugin has been tested successfully on MSM8916 or MSM8974
> SoCs, and there is some ongoing work to make it work on SDM845 and
> similar platforms.
I wonder if libqrtr-glib has other use than qcom-soc plugin.
Originally I thought there is more use and thus I add it to buildroot,
but if it's just for qcom-soc, it should be added:
ifeq ($(BR2_PACKAGE_LIBQRTR_GLIB),y)
MODEM_MANAGER_CONF_OPTS += --enable-plugin-qcom-soc
else
MODEM_MANAGER_CONF_OPTS += --disable-plugin-qcom-soc
endif
Although it will not be useful until anybody tries to add some phone based
defconfigs into buildroot.
Kind regards,
Petr
next prev parent reply other threads:[~2021-03-31 18:24 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
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 [this message]
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=YGS+cAr0P67MDjFa@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