All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henning Heinold <heinold@inf.fu-berlin.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New meta-cubox layer
Date: Thu, 4 Apr 2013 09:32:59 +0200	[thread overview]
Message-ID: <20130404073259.GA8722@mi.fu-berlin.de> (raw)
In-Reply-To: <515C5DE6.6040702@pseudoterminal.org>

On Wed, Apr 03, 2013 at 06:50:46PM +0200, Carlos Rafael Giani wrote:
> Hello,
> 
> I have created a BSP layer for the SolidRun Cubox platform. Informations about this device can be found athttp://solid-run.com/cubox  .
> The layer itself is hosted athttps://github.com/dv1/meta-cubox  .
> 
> This layer introduces a new machine, new tunes for the CuBox' Marvell PJ4 processor, in addition to the platform specific recipes for hardware video acceleration and EGL,OpenGL ES,OpenVG support. Both hardfp and softfp are supported.
> The 3D accelerator and the hardware accelerated video engine (called vMeta) require some closed source components. The recipes pick the right ones depending on whether softpfp or hardfp is used.
> 
> It also copies the generated uImage into the rootfs (as expected by the bootloader), and autogenerates a boot.scr out of an included boot script using uboot-mkimage.
> The resulting tarball is extracted on an SD card, and the device can be booted.
> 
> A new xorg driver and a customized xorg.conf are included.
> 
> I'm open to feedback, patches, suggestions.
> 
> Thanks

Hi,

nice work, but I wonder why the u-boot needs a boot.scr. Is it that old or can you switch it over to uEnv.txt so it is easier for people
to change kernel cmdline and other u-boot config stuff.

Bye Henning



  parent reply	other threads:[~2013-04-04  7:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 16:50 New meta-cubox layer Carlos Rafael Giani
2013-04-03 17:52 ` Khem Raj
2013-04-03 18:12   ` Carlos Rafael Giani
2013-04-03 18:05 ` Burton, Ross
2013-04-03 18:11   ` Carlos Rafael Giani
2013-04-03 18:37     ` Burton, Ross
2013-04-03 18:38 ` Koen Kooi
2013-04-03 19:04   ` Carlos Rafael Giani
2013-04-04  9:45     ` Koen Kooi
2013-04-03 19:34   ` Philip Balister
2013-04-03 19:57     ` Koen Kooi
2013-04-03 20:07       ` Philip Balister
2013-04-03 20:19         ` Koen Kooi
2013-04-03 20:49           ` Carlos Rafael Giani
2013-04-03 21:45             ` Otavio Salvador
2013-04-03 22:21               ` Khem Raj
2013-04-03 22:29                 ` Carlos Rafael Giani
2013-04-03 22:40                   ` Martin Jansa
2013-04-03 22:49                     ` Carlos Rafael Giani
2013-04-03 21:43     ` Otavio Salvador
2013-04-03 22:52       ` Philip Balister
2013-04-04  6:01         ` Koen Kooi
2013-04-04  5:53       ` Koen Kooi
2013-04-04  7:32 ` Henning Heinold [this message]
2013-04-04 16:08   ` Carlos Rafael Giani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130404073259.GA8722@mi.fu-berlin.de \
    --to=heinold@inf.fu-berlin.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.