buildroot

Bluetooth on Raspberry Pi Zero W, using buildroot

由 那年仲夏 提交于 2019-12-08 06:42:59
问题 I'm trying to get the onboard Broadcom bluetooth working in a Buildroot 2017.08 built linux on the Raspberry Pi Zero W . It's not showing me the adapter. Bluetooth USB dongles do work. Things I've already done: Added rpi-bt-firmware Added Bluez-tools and Bluez5-utils Kernel compiled with all sorts of Bluetooth support Loaded bluetooth modules: bluetooth, bnep, btbcm, hci_uart rfkill list (shows no bluetooth devices) rfkill unblock bluetooth (just in case) After boot I'm manually starting

What is the minimal nesesary file subset, required to AMD OpenCL work on Linux?

由 痴心易碎 提交于 2019-12-07 20:48:26
问题 I've built Linux Kernel, with means of the buildroot. I've incorporated opensource amdgpu driver and required firmwares into it. Driver is fine, detecting GPUs, mode setting acts good, adjusting resolution for "small text", and command line shows up after boot. Now I require to run OpenCL program. I manually unpacked files from amdgpu-pro driver(rhel7 variant) and assembled skeleton fs then copied what I thought was required. OpenCL does not recognise any devices and clinfo utility throws cl:

buildroot - how to change kernel version string

由 巧了我就是萌 提交于 2019-12-07 09:21:35
问题 I work on SAM9G25 EK board with buildroot and Armstrong linux (Linux4sam). My script is creating linux version "2.6.39+" and this "+" is confusing (/lib/modules folder etc.). I want to remove it. I found only two files .uImage.cmd, and kernel.release that contains this string, but both are generated. Where is this string created ? 回答1: You have a .config ? Look in there for the value assigned to CONFIG_LOCALVERSION . To have no local version specifed in the kernel's release, either remove

buildroot for arm kernel defconfig

由 我是研究僧i 提交于 2019-12-07 06:22:50
问题 I am trying to build a buildroot with kernel image, and after doing make menuconfig and make , I am getting: No kernel defconfig name specified, check your BR2_LINUX_KERNEL_DEFCONFIG setting I can set a string to the defconfig , but I don't know what to put there. My target system is an AT91SAM9RL board. edit : I found out there are some pre-made config files to some devices, actually not exactly matching to my target. 回答1: You can issue the default configuration process by running make xxx

Multiple files created by arecord

由 对着背影说爱祢 提交于 2019-12-07 02:32:46
问题 I've made custom distribution using buildroot, with hard-flow for ARMv7 processor. Everything is working except.... # arecord -D hw:0,0 -fdat -d 5 test.wav This makes multiple files. Thousands of them. -rw-r--r-- 1 root root 958508 Jan 1 00:19 test-01.wav -rw-r--r-- 1 root root 44 Jan 1 00:19 test-02.wav -rw-r--r-- 1 root root 44 Jan 1 00:19 test-03.wav -rw-r--r-- 1 root root 44 Jan 1 00:19 test-04.wav -rw-r--r-- 1 root root 44 Jan 1 00:19 test-05.wav -rw-r--r-- 1 root root 44 Jan 1 00:19

How to pass extra custom ./configure autotools options to a Buildroot package?

由 只谈情不闲聊 提交于 2019-12-06 12:06:28
E.g., I want to add the options --enable-foo --enable-bar to a ./configure command. Many ./configure options can be set indirectly through BR2_ configs, but many software have so many options that it would be infeasible to have one BR2_ config for every possible ./configure option. Is there a general mechanism that works for all autotools packages? I think there is no current general method as of 2017.02, since package/pkg-autotools.mk contains: # Configure package for target define $(2)_CONFIGURE_CMDS (cd $$($$(PKG)_SRCDIR) && rm -rf config.cache && \ $$(TARGET_CONFIGURE_OPTS) \ $$(TARGET

How to control the rpmbuild buildroot and install directory

由 若如初见. 提交于 2019-12-06 09:15:20
问题 I am confused about some directories in rpmbuild. 1: buildroot: which should be used to store the files that are supposed to be installed when the binary package is installed by an end-user. Questions: how to control this directory? What does BuildRoot mean? $ cat 3.spec .. BuildRoot: /opt/abc .. %prep echo %{buildroot} echo $RPM_BUILD_ROOT whatever I set the BuildRoot to, I get the result which was defined in /usr/lib/rpm/macros . If I define %buildroot in ~/.rpmmacros , I will get the

What is the minimal nesesary file subset, required to AMD OpenCL work on Linux?

由 我的梦境 提交于 2019-12-06 06:17:21
I've built Linux Kernel, with means of the buildroot. I've incorporated opensource amdgpu driver and required firmwares into it. Driver is fine, detecting GPUs, mode setting acts good, adjusting resolution for "small text", and command line shows up after boot. Now I require to run OpenCL program. I manually unpacked files from amdgpu-pro driver(rhel7 variant) and assembled skeleton fs then copied what I thought was required. OpenCL does not recognise any devices and clinfo utility throws cl::error from cl::getPlatformIDs() call. What are exactly files required for OpenCL to fully work on

STM32F746-DISCO运行Linux4.19

由 自闭症网瘾萝莉.ら 提交于 2019-12-05 22:10:54
STM32F746-DISCO运行Linux4.19 Linux Kernel 主线linux已经提供对无MMU的处理器的支持，configs中已经存在stm32_defconfig，DTS中包含：stm32f746-disco；因此只需要编译即可。 下载主线源码: http://cdn.kernel.org/pub/linux/kernel/v4.x 安装交叉编译链，可以使用之前编译uboot的arm-none-eabi-gcc，但是这个是编译链线程模式是single，而不是posix，也就是说虽然这个编译链可以编译内核和根文件系统，但是不能编译linux应用程序。如果需要支持编译linux应用程序（一般要支持，不然移植linux干嘛--！），则需要自己去构建交叉编译链，网上讲解的比较详细，不过我推荐使用Buildroot来构建支持stm32的交叉编译链，简单快捷，当然也可以用Buildroot来构建内核和根文件系统。 根文件系统 根文件系统可以使用busybox构建，也可以使用buildroot构建。 elinux.org提供了一个使用busybox编译好的Ramdisk最小系统， File:Stm32 mini rootfs.cpio.bz2 , 但需要做如下改动： 使用initramfs，将下载的Stm32_mini_rootfs.cpio.bz2解压，先解压成cpio文件

buildroot - how to change kernel version string

由 痴心易碎 提交于 2019-12-05 17:30:57
I work on SAM9G25 EK board with buildroot and Armstrong linux (Linux4sam). My script is creating linux version "2.6.39+" and this "+" is confusing (/lib/modules folder etc.). I want to remove it. I found only two files .uImage.cmd, and kernel.release that contains this string, but both are generated. Where is this string created ? You have a .config ? Look in there for the value assigned to CONFIG_LOCALVERSION . To have no local version specifed in the kernel's release, either remove CONFIG_LOCALVERSION or comment it out by starting the line containing it by a # . The default shall be: #CONFIG
订阅 buildroot