On Thu, 2008-06-05 at 16:12 -0400, Jeff Garzik wrote:
quoted text
> Well, I should ask, is this purely an internal build detail?
>
> The developer (and user) should never ever see a .ihex file, outside of 
> an active kernel compile.  Wrapping the original firmware makes it more 
> difficult to verify, compare and/or change.  In-tree, we should see the 
> vendor firmware blobs as shipped, with no wrapping or modification or 
> anything.

It's a build-and-shipping detail, at least in the kernel source tree.

Rather than putting binary blobs into git (which admittedly we could,
but it's suboptimal), we just run them through 'objcopy -Oihex' first.

It's not 'wrapped'; it's not any more difficult to verify, compare or
change.

-- 
dwmw2

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/