On 02/06/2012 10:33 PM, Chris Tyler wrote:
But back to the original question: what's the optimal way to package an
installable image? I see several valid options:
(1)- Per-platform image with MBR plus one or more partitions, with the
last partition shipped as minimal length and resizable
On 02/07/2012 10:20 PM, Peter Robinson wrote:
On Tue, Feb 7, 2012 at 9:15 PM, Mark Langsdorf
mark.langsd...@calxeda.com wrote:
On 02/06/2012 10:33 PM, Chris Tyler wrote:
But back to the original question: what's the optimal way to package an
installable image? I see several valid options:
On Tue, Feb 7, 2012 at 10:26 PM, Gordan Bobic gor...@bobich.net wrote:
On 02/07/2012 10:20 PM, Peter Robinson wrote:
On Tue, Feb 7, 2012 at 9:15 PM, Mark Langsdorf
mark.langsd...@calxeda.com wrote:
On 02/06/2012 10:33 PM, Chris Tyler wrote:
But back to the original question: what's the
On Fri, 2012-02-03 at 16:25 -0800, Brendan Conoboy wrote:
The support grid is really just 2x2: You're either armv5tel or armv7hl.
You either need a separate partition for bootloader bits (omap, etc
scenario) or you don't (tegra scenario). Putting together tarball that
has everything a
Gordan Bobic gor...@bobich.net writes:
Kernels are SoC specific. Not quite as narrowly specialized as device
specific, but it's still not going to be a one-size-fits all, at least
not any time soon (probably years).
For example, if you have a Marvell Kirkwood kernel, you could use that
On Fri, Feb 3, 2012 at 1:50 PM, Derek Atkins warl...@mit.edu wrote:
Gordan Bobic gor...@bobich.net writes:
Kernels are SoC specific. Not quite as narrowly specialized as device
specific, but it's still not going to be a one-size-fits all, at least
not any time soon (probably years).
For
On 02/02/2012 02:41 PM, Gordan Bobic wrote:
Not going to happen, sadly. The rootfs is common across all the devices
(armv5tel for soft-float, armv7hl for hard-float).
Hold up, there's a middle ground that we can shoot for here, even prior
to everybody getting onboard with FDT.
Kernels are
