A Snappy Gumstix Overo

[Ash Charles]

Hi Alexander,

Great to hear from you---long time no talk indeed :).

I submitted the snap here:
https://myapps.developer.ubuntu.com/dev/click-apps/2476/
(FWIW, when I build the package, click-review gets angry and says
"(MANUAL REVIEW) type 'oem' not allowed").

On Sun, Apr 26, 2015 at 9:40 AM, Alexander Sack <asac at canonical.com> wrote:
> oh i forgot in my other mail to explain that signing happens through
> uploading to store! Is pretty trivial for you as you reuse our
> official enablement/kernel and just have a custom dtb and bootloader.
Is 'flashtool-assets' totally superseded by oem packages?  I got hung
up on this when I first started playing around.
Being able to use a stock kernel made it really easy. I actually
tested out a custom kernel too as some patches for our latest wireless
chip (Wilink8) aren't yet mainlined but packing/unpacking the ramdisk
got to be a pain.
What is the best source for the ramdisk? The snappy-device-builder
grabs [1], adds the custom kernel, and then re-packs for use as
"--device-part"

[1] http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/vivid-preinstalled-core-armhf.device.tar.gz

<snip>
> this is a cool showcase how to 'freeride' our officially supported
> enablement by just providing your board specifics in oem snap. Thanks
> for this! Should be similarly trivial for plenty other boards like
> panda beagleboard etc...
And DuoVero (OMAP4 like panda) and Pepper (AM335x like beaglebone) hehehe...
<snip>
> We don't have an overo in our teams. 20 seconds sounds a bit too long,
> but not sure how the IO is on overo. If you want to debug you find us
> on #snappy on freenode as well!
Cool--thanks. I've found that SD cards vary widely in performance so I
may try loading the initrd from NAND just to test.

--Ash