Closed
Bug 1195089
Opened 10 years ago
Closed 10 years ago
Building bootable images for device without a device tree (dt.img) for the kernel fails
Categories
(Firefox OS Graveyard :: B2gInstaller, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
FxOS-S5 (21Aug)
People
(Reporter: gerard-majax, Assigned: gerard-majax)
References
Details
(Whiteboard: [systemsfe])
Attachments
(1 file)
> Building bootable image /tmp/b2g-installer/aries/content/BOOT /tmp/b2g-installer/aries/images/boot.img about.js:213:3
> This device hasDeviceTree? false
So we properly detect we have no dt.img, but ...
> Prepared options Object { kernel: "/tmp/b2g-installer/aries/content/BO…", ramdisk: "/tmp/b2g-installer/aries/content/BO…", dt: "/tmp/b2g-installer/aries/content/BO…", output: "/tmp/b2g-installer/aries/images/boo…", cmdline: "androidboot.hardware=qcom user_debu…", pagesize: "2048", base: "0x00000000" }
We still pass it to the build process :(
Assignee | ||
Comment 1•10 years ago
|
||
Assignee: nobody → lissyx+mozillians
Status: NEW → ASSIGNED
Attachment #8648461 -
Flags: review?(dale)
Assignee | ||
Updated•10 years ago
|
Whiteboard: [systemsfe]
Target Milestone: --- → FxOS-S5 (21Aug)
Comment 2•10 years ago
|
||
Comment on attachment 8648461 [details] [review]
PR
Looks good to me, cheers
Attachment #8648461 -
Flags: review?(dale) → review+
Assignee | ||
Comment 3•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•