[meta-freescale] Wandboard Quad experience (good!)

[John Weber]

Hi Chris,

First off - thanks for trying out the kernel.  Let me know if you see
anything that needs to be fixed.  Patches are welcome, of course.

I chatted with Otavio about this issue because I'm working on getting Quad
up and running tonight.  He already has a patch to submit.  If you're
interested in trying this tonight, all you need to do is rename:

meta-fsl-arm-extra/recipes-bsp/broadcom-nvram-config/files/wandboard-dual

to

meta-fsl-arm-extra/recipes-bsp/broadcom-nvram-config/files/wandboard
(without the '-dual')

When we did this in the beginning, all we had with Wifi on it was the
Dual.  Now we have Quad, so we need to use a common directory.

John



On Tue, Jul 9, 2013 at 6:05 PM, Chris Tapp <opensource at keylevel.com> wrote:

>
> On 9 Jul 2013, at 23:03, Chris Tapp wrote:
>
> >
> > On 9 Jul 2013, at 22:51, Otavio Salvador wrote:
> >
> >> On Tue, Jul 9, 2013 at 6:38 PM, Chris Tapp <opensource at keylevel.com>
> wrote:
> >>> Thanks to help from Otavio and others, I now have an image building
> for the Wandboard Quad.
> >>>
> >>> I've built a custom OpenGLES application running under EGL (which I
> normally run on a Cedar Trail platform) and it's mostly running as expected
> - just need to work out why my gstreamer pipeline isn't working.
> >>>
> >>> The only bit that I had to work round was broadcom-nvram-config, which
> resulted in:
> >>>
> >>> NOTE: Resolving any missing task queue dependencies
> >>> ERROR: Nothing RPROVIDES 'linux-firmware-INVALID' (but
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/
> broadcom-nvram-config.bb RDEPENDS on or otherwise requires it)
> >>> NOTE: Runtime target 'linux-firmware-INVALID' is unbuildable,
> removing...
> >>>
> >>> I got round this by commenting out:
> >>>
> >>> MACHINE_EXTRA_RRECOMMENDS += " broadcom-nvram-config"
> >>
> >> I fixed this and pused this for master-next; please confirm it works :-)
> >
> > Yes it does. Thank you :-)
>
> Or not... I'm getting a fetcher failure:
>
> WARNING: Failed to fetch URL file://nvram.txt, attempting MIRRORS if
> available
> ERROR: Fetcher failure: Unable to find file file://nvram.txt anywhere. The
> paths that were searched were:
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config-1.0/arm
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config-1.0/armv7a
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config-1.0/mx6
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config-1.0/mx6q
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config-1.0/wandboard
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config-1.0/wandboard-quad
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config-1.0/poky
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config-1.0/
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config/arm
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config/armv7a
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config/mx6
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config/mx6q
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config/wandboard
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config/wandboard-quad
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config/poky
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config/
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/files/arm
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/files/armv7a
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/files/mx6
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/files/mx6q
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/files/wandboard
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/files/wandboard-quad
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/files/poky
>
> /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/files/
>     /media/SSD-RAID/build-danny-wandboard/../yocto-downloads
> ERROR: Function failed: Fetcher failure for URL: 'file://nvram.txt'.
> Unable to fetch URL from any source.
> ERROR: Task 4
> (/media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/
> broadcom-nvram-config.bb, do_fetch) failed with exit code '1'
>
> >
> >> --
> >> Otavio Salvador                             O.S. Systems
> >> http://www.ossystems.com.br        http://projetos.ossystems.com.br
> >> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> >
> > Chris Tapp
> >
> > opensource at keylevel.com
> > www.keylevel.com
> >
> >
> >
> > _______________________________________________
> > meta-freescale mailing list
> > meta-freescale at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-freescale
>
> Chris Tapp
>
> opensource at keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20130709/62548b08/attachment.html>