Closed
Bug 1016940
Opened 10 years ago
Closed 10 years ago
[Flame] Include device tree in boot.img
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gerard-majax, Assigned: gerard-majax)
References
Details
(Whiteboard: [systemsfe])
Attachments
(1 file)
Now that we have proper bits in build/core/Makefile, we need to be ready for when the kernel will be buildable.
Assignee | ||
Comment 1•10 years ago
|
||
Please find attached a link to the github pull request. We just need to remove those bits now, everything should be fine.
Attachment #8430012 -
Flags: review?(mwu)
Updated•10 years ago
|
Attachment #8430012 -
Flags: review?(mwu) → review+
Assignee | ||
Comment 2•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 3•10 years ago
|
||
Reverted for strongly suspecting this to be the cause of mass Flame bustage.
https://github.com/mozilla-b2g/device-flame/commit/218bcff6200f9b9e054467da963b7209e43ad287
https://tbpl.mozilla.org/php/getParsedLog.php?id=40638814&tree=Mozilla-B2g30-v1.4 etc...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 4•10 years ago
|
||
Looks like we cannot land this until we use the proper kernel repo ...
Comment 5•10 years ago
|
||
Please can we test things like this locally before pushing? :-)
Comment 6•10 years ago
|
||
> 07:28:57 INFO - => Found 0 unique DTB(s)
> 07:28:57 INFO - chmod: cannot access `out/target/product/flame/dt.img': No such file or directory
If this means what I think it does, then we need to delete `BOARD_KERNEL_SEPARATED_DT := false` and `TARGET_NO_KERNEL := true` in the same commit, or at least the same push — we won't have any DTB files unless the kernel build is run, and the boot.img won't work without the device tree.
Comment 7•10 years ago
|
||
(In reply to Ed Morley [:edmorley UTC+0] from comment #5)
> Please can we test things like this locally before pushing? :-)
For what it's worth, that wouldn't have caught the breakage without a manual clobber of out/target, if an earlier build in the same tree had already built the kernel.
A try run (via gecko/b2g/config/flame/sources.xml) would have caught it, but we currently can't do the Flame image build on try.
Updated•10 years ago
|
Whiteboard: [systemsfe]
Assignee | ||
Comment 8•10 years ago
|
||
Fixed by bug 1004195
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•