d959966b41
dahdi-linux provides kernel modules to drive a variety of telephony cards, ranging from low-end one-channel to higher-end multi-channel cards. It also provides headers for userland to talk to those cards. With a bit of love, dahdi-linux can use our kernel-module infrastructure. Wee! :-) Still, there are a few specificities about dahdi-linux. First, it needs to install a few binary firmware blobs, which it wants to download at install time. Since we do want to be able to do completely off-line builds, we need to downlaod them manually. So we have the full list of firmware blobs (even if some can only be used on an i386/x86_64 target, we still uconditionally download them), for which we have locally-computed sha256 (no hash provided by upstream for the blobs). Second, the install procedure for the firmware blobs needs to have access to the Linux kernel .config file, so it can decide whether to install the blobs or not. We can force not to install them, but we can't force to install them... :-/ And anyway, we'd have to do the same check as is already done by dahdi-linux, so no need to duplicate that. Finally, the licensing is relatively weird. Although it is obvious and straightforward for the most part of dahdi-linux, consisting of mostly GPLv2 and a few LGPLv2.1, there is one gotcha. Of the firmware blobs, one is provided as a .o file, with no licensing information whatsoever, without any source available from upstream, but is directly linked to a GPLv2 file. This is very concerning, but there is not much we can do about it, except delegate to the legal reviewer whether that is acceptable or not. AS an aside, dahdi-linux drivers do not build with a kernel 4.0 or later, as it uses internals that have been removed in linux-4.0. There has been no update upstream dahdi-linux to fix that. There's not much we can do, except warn the user in the help text. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> [Arnout: use SPDX license names and add hashes for license files] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .defconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitlab-ci.yml.in | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on Freenode IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches