All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	 meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH] devregs: Add recipe
Date: Tue, 06 Jan 2015 10:41:44 -0700	[thread overview]
Message-ID: <54AC1E58.6010406@boundarydevices.com> (raw)
In-Reply-To: <1420564560-4388-1-git-send-email-otavio@ossystems.com.br>

Thanks Otavio,

On 01/06/2015 10:16 AM, Otavio Salvador wrote:
> This includes the Boundary Devices' devregs tool which allows for
> reading and writting of registers using /dev/mem.
> 
> It currently has support for i.MX51, i.MX53, i.MX6Q and i.MX6DL SoC
> families but other SoCs can be easily added including extra .dat
> files.
> 
> Change-Id: Ic04a90e7d1db8d87f43f5574792aa73885f16d66
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>  recipes-devtools/devregs/devregs_git.bb | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>  create mode 100644 recipes-devtools/devregs/devregs_git.bb
> 
> diff --git a/recipes-devtools/devregs/devregs_git.bb b/recipes-devtools/devregs/devregs_git.bb
> new file mode 100644
> index 0000000..3bac55a
> --- /dev/null
> +++ b/recipes-devtools/devregs/devregs_git.bb
> @@ -0,0 +1,13 @@
> +DESCRIPTION = "i.MX Register tool"
> +SECTION = "devel"
> +LICENSE = "GPL-1"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=5003fa041d799dd5dd5f646b74e36924"
> +
> +SRCREV = "34ed402b92920864b89e0fd1e76bae3aa340baaa"
> +SRC_URI = "git://github.com/boundarydevices/devregs.git;protocol=http"
> +
> +PV = "1.0+${SRCPV}"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit autotools
> 

Acked-by: Eric Nelson <eric.nelson@boundarydevices.com>

This will save me time when pulling it into other projects.


      reply	other threads:[~2015-01-06 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 17:16 [meta-fsl-arm][PATCH] devregs: Add recipe Otavio Salvador
2015-01-06 17:41 ` Eric Nelson [this message]

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=54AC1E58.6010406@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.