[PATCH 7/8] ath10k-ct: Support qcom,ath10k-calibration-data-base64

Christian Marangi ansuelsmth at gmail.com
Thu Jan 5 15:05:44 PST 2023

On Thu, Jan 05, 2023 at 02:03:24PM -0800, Brian Norris wrote:
> In case you are open to giving more helpful tips to a relative
> newcomer to openwrt development:
> On Thu, Jan 5, 2023 at 11:59 AM Brian Norris
> <computersforpeace at gmail.com> wrote:
> > I'll just need to
> > force a 'base64' utility into these images
> This is turning out to be nontrivial. The only in-tree base64 tool is
> a busybox tool, and it's not enabled in the default busybox
> configuration. I don't see an easy way for a target to change this
> default. I *do* see package dependencies that do this (like
> DEPENDS:=+ at BUSYBOX_CONFIG_<feature>), but I don't think that works in
> a target (e.g., adding to DEVICE_PACKAGES).
> Do I need to create some intermediate/stub package just to express the
> dependency, or is there some better way?

In theory there is [1] coreutils-base64 as a separate package but I
think we have to move that to core packages as it's part of the feeds

Just for testing can you test if that package suits your need for a
userspace solution?

[1] https://openwrt.org/packages/pkgdata/coreutils-base64


More information about the openwrt-devel mailing list