Opened 11 years ago
Closed 11 years ago
#940 closed task (fixed)
Fix kernel build instructions
| Reported by: | Andrew Bradford | Owned by: | Andrew Bradford |
|---|---|---|---|
| Priority: | major | Milestone: | CLFS Embedded 1.0.0 |
| Component: | BOOK | Version: | CLFS Embedded GIT |
| Keywords: | Cc: |
Description
Kernel build right now is all sorts of silly.
Sadly, many embedded dev kits are not able to boot mainline Linux kernels but often ship with either an evil vendor source tree or just an evil vendor binary. As long as the evil vendor's kernel is newer than the headers we install, that'll be OK.
But how exactly does one instruct someone to build a kernel for an embedded board? Since there's so many damn choices in menuconfig that really do matter, let alone device tree.
Would a viable path be to build for a QEMU target but say, "Do it like this, just for your board."?
Change History (2)
comment:1 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Fixed as of SHA: d4c0817e9d029bc956e13c278248ed1d29c06e3a