Hi, I wanted to sync up on where things are with this, and as I understand, there&#39;s some confusion still about how we should get the available kernel and/or images for testing fast models.<br><br>First off, it seems there is no way to just take a kernel .axf as we thought because the boot args are wrapped into it as well.  Is there really no way to inject that stuff after build time?<br>

<br>Is it worth revisiting whether we should have proper hwpacks for fast models?  I know there&#39;s the 2G max sd size issue with that, but if that&#39;s something arm can fix, or if we have another way around it, would that help?<br>

<br>Finally, I feel like we&#39;ve chased a pretty messy route to get fast models supported here, which will ultimately break completely when we try to get android running also.  Please correct me if I&#39;m wrong here, but it seems the &quot;recommended&quot; approach is currently:<br>

lava takes as input: git tree for the kernel we want to build, defconfig to use, and rootfs tarball<br>lava builds the kernel (lava doesn&#39;t do this currently, complicating things for us quite a bit - would be better if this step could be done externally, like in jenkins where we do the kernel ci builds)<br>

lava pushes the build axf to another system where we have the fast models software installed, provisions the rootfs for booting over nfs<br>lava boots the system under fast models on this other machine, runs tests, gathers results, etc<br>

<br>Is that pretty close Zygmunt? Is there something more straightforward and less fragile that we can do here?<br><br>Thanks,<br>Paul Larson<br>