[INSTRM-31] Replace unnecessarily complicated Yocto build for BEEs Created: 08/Dec/16 Updated: 16/Mar/17 Resolved: 16/Mar/17 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | cloomis | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
I chose Yocto to construct the first BEE images, mostly because I was expecting to have to fiddle with performance and power issues. I now believe that we only need the PREEMPT patches and that the chipset does not give any useful leverage to the OS to control power. Yocto is surprisingly complicated, and makes building new images difficult. This just caused trouble at LAM, since the gatevalve (ADIO) kernel driver could not be built quickly. So we should switch to something (much) simpler. |
| Comments |
| Comment by cloomis [ 16/Mar/17 ] |
|
In 2017-02 I switched to a recent simple debian 8 build, which I then image-copied to the new r1, the b1, and the b9 pie-pans. I think the image if OK, but am not terribly happy about how package version are "saved". |