eDSP | platform DSP library written in C++ | Audio Utils library

The test passes if you force the enumeration by calling .ToList() on the result.

For example:

Your target may not have dedicated hardware for encryption, and you therefore may not have any openssl crypto-engine implementation available on your platform, nor a version of openssl compiled with support for crypto-engines.

You can check by executing ls: /usr/lib/engines-1.1, since this is the location specified in the output for the openssl version -a command you executed. If no dynamic libraries are present, or the directory does not exist, this is likely that you don't have any support for crypto-engines currently available on your system.

In this case, you will have to re-build mosquitto with the CFLAGS=-DOPENSSL_NO_ENGINE option, so that mosquitto will not attempt to load any (non-existing) openssl crypto-engine at startup.

Solved it. It turned out that my make menuconfig was incomplete.

OK. I was able to solve the problem for the most part. Focusing on /proc/cpuinfo only was not good idea. Instead, I managed to get interesting hardware info like that:

Get smartphone manufacturer and model. In my case the output is: "samsung SM-J730F":

So miracle of miracles I came across the answer totally by accident. I'd like to share in case anybody else comes across this and similarly bangs their heads for months.

In a totally unrelated change for another system I'm working on using this block driver, I made a change today and tried it on the pi4 and like magic it's all working.

What was the change? Not at all where I was looking....

So I register a callback with blk_queue_make_request not blk_init_queue. I don't handle the request queue, I handle the bios in the block request directly.

In so doing, you are told: https://www.kernel.org/doc/htmldocs/kernel-api/API-blk-queue-make-request.html

"The driver that does this must be able to deal appropriately with buffers in “highmemory”. This can be accomplished by either calling __bio_kmap_atomic to get a temporary kernel mapping, or by calling blk_queue_bounce to create a buffer in normal memory. "

Well, I had been achieving that with calls to kmap_atomic when I wanted to get the buffer. Today I read that there's a limited number of slots for those memory mappings and you should only call that if you're in an interrupt context and can't go to sleep, because the kmap_atomic call pulls from the reserved pile so it doesn't have to allocate on the call and possibly be put to sleep.

But my kernel module can sleep, so I changed the call to kmap() and... like magic... it's working.

So I'm thinking the failure cases were where kmap_atomic was failing and I wasn't catching or noticing, or possibly, something is wrong with kmap_atomic on the pi4 or on the interaction between the kernel in that case or something. I'll play more and see if I can tease out what's going on, but the trick is something's wrong with the way I was calling kmap_atomic.

After a little playing around...

I solved my problem.

Steps:

1) Copy need library from android phone (libgui.so, libui.so, libcutils.so, libutils.so, libbinder.so).

2) Add in sys_root (when save ndk lib code files from Android Android 6_r1 libs: utils, cutils, system, log, hardware, system, ports, core, include/gui, include/ui, include/binder). You can run this code for find your system root:

My first bet are incompatible ABI. Your binary:

The package google-cloud is deprecated and should not be used.

Normally you would import the library that you need.

Example: google-cloud-core and google-cloud-storage.

google-cloud deprecation notice

-mfpu=neon should solve the problem.

BTW, do you honestly expect just including the header file will do the trick?

NEON has tons of instructions that aren't available on Intel machines, especially in terms of permutation.

What you will get is lots of vtbl instructions that come with nasty latencies here and there that consumes cycles like crazy.

Simply relying on someone else's generic solution cannot be called optimization IMO.