hy-l
hy-l
I'd like to build the same kinda "native" compiler too, for android. If compiling gcc with the "configure" script, I need to provide the option `--build=x86_64-linux-gnu --host=aarch64-linux-android --target=aarch64-linux-android` ~~but I...
@concatime What is your build machine's architecture? If it's x86_64, compiling with `TARGET = x86_64-linux-musl` will produce the native compiler you needed directly, there's no need to use qemu.
You can build again with CC/CXX pointed at the toolchain you have just got after the first pass. (Well... How did my message jump to the upside? ;p)
Hi, I've uploaded a short sample video which could represent the issue. https://drive.google.com/file/d/1SPPyCS0_6VEaNWsputJohXAYRlqcFTEn/view?usp=drivesdk HY Liu
Hi, @matthiasseemoo I'm a bit confused by the difference between "ROM" and "firmware" described in README. > The Wi-Fi firmware consists of a read-only part stored in the ROM of...
Hi - again, I've done some diggings on my phone these days, here are some things I've found out: - There are some dot files in `/data/misc/conn` that are created...
Although I couldn't understand what you said very well, I just think this because the system auto load the original driver rather than the one you compiled after a reboot....
No, these commands only backup and install the firmware in '/lib/firmware/brcm/' directory, and `make install-firmware` also uses `rmmod` to unload the system's `brcmfmac.ko` kernel module and `insmod` to insert the...
could it be because you stripped the module?
no, 'strip the module' means that you ran the 'strip' command on the .ko file to reduce its size. i guessed so because it was the mistake i made before,...