From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] dfu-programmer: USB Device Firmware Upgrade utility (special atmel-version)
Date: Thu, 8 Apr 2010 19:29:53 +0200 [thread overview]
Message-ID: <20100408172953.GG3269@jama> (raw)
In-Reply-To: <alpine.DEB.1.10.1004081733510.3264@vitus.devnet.local>
On Thu, Apr 08, 2010 at 05:37:41PM +0200, Vitus Jensen wrote:
> Add recipes for version 0.5.2 and the current head of the subversion
> repository. dfu-programmer is DFU utility supporting Atmel chips
> with a USB bootloader (which aren't supported by dfu-util).
>
> Signed-off-by: Vitus Jensen <vjensen@gmx.de>
> diff --git a/conf/checksums.ini b/conf/checksums.ini
> index 3c6f712..73f5901 100644
> --- a/conf/checksums.ini
> +++ b/conf/checksums.ini
> @@ -5258,6 +5258,10 @@ sha256=3b15515693bae1ebd14d914e46d388edfec2175829ea1576a7a0c8606ebbe639
> md5=be12c0132a1ae118cbf5e79d98427c1d
> sha256=ec382c90af3ef2f49695ff14a4d6521e58ac482c4e29d6c9ebca8768f699c191
>
> +[http://downloads.sourceforge.net/project/dfu-programmer/dfu-programmer/0.5.2/dfu-programmer-0.5.2.tar.gz]
> +md5=ce882d37383df698a1c530080724b191
> +sha256=e3c8bc1429fe1681c56ddc14fb05d29a7933aac566d13f894dca6fd916829cb9
> +
> [http://pknet.com/~joe/dgen-sdl-1.23.tar.gz]
> md5=b1896c1b21ddb152626aec2e8a157a3a
> sha256=44396b3b324433187cf7082d1059cd9f519f02accddd667e627a57ff8514d436
> diff --git a/conf/distro/include/sane-srcrevs.inc b/conf/distro/include/sane-srcrevs.inc
> index 902c844..982632c 100644
> --- a/conf/distro/include/sane-srcrevs.inc
> +++ b/conf/distro/include/sane-srcrevs.inc
> @@ -41,6 +41,7 @@ SRCREV_pn-contact ?= "1410"
> SRCREV_pn-dasher-gpe ?= "1251"
> SRCREV_pn-dbus-c++ ?= "13131"
> SRCREV_pn-dbus-c++-native ?= "13131"
> +SRCREV_pn-dfu-programmer ?= "93"
> SRCREV_pn-dfu-util ?= "4160"
> SRCREV_pn-dfu-util-native ?= "4160"
> SRCREV_pn-disko ?= "f52597b8d5d584811cbe8f9e0bf25ea372526953"
This doesn't seem applicable after SRCREV moving to recipes last week.
Please send separate patch for org.openembedded.dev with SRCREV as well
as checksums in recipes and for stable/2009 (you can put SRCREV to
recipe as long as it's sane SRCREV not AUTOREV).
> +PV = "0.5.2+svnr${SRCREV}"
In org.openembedded.dev it's always "+svnr${SRCPV}" for svn recipes
(hopefully soon also unified for git recipes).
Thanks
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2010-04-08 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 8:19 [PATCH] dfu-programmer: USB Device Firmware Upgrade utility (special atmel-version) Vitus Jensen
2010-04-08 8:32 ` Vitus Jensen
2010-04-08 8:59 ` Stefan Schmidt
2010-04-08 9:32 ` Vitus Jensen
2010-04-08 11:09 ` Stefan Schmidt
2010-04-08 8:35 ` Stefan Schmidt
2010-04-08 15:33 ` Vitus Jensen
2010-04-08 15:37 ` [PATCH v2] " Vitus Jensen
2010-04-08 17:29 ` Martin Jansa [this message]
2010-04-12 5:04 ` Vitus Jensen
2010-04-16 14:13 ` [PATCH v3] " Vitus Jensen
2010-04-16 14:41 ` Stefan Schmidt
2010-04-16 14:50 ` Vitus Jensen
2010-04-16 14:57 ` Stefan Schmidt
2010-04-16 15:05 ` Stefan Schmidt
2010-04-16 15:12 ` Vitus Jensen
2010-06-25 8:08 ` [PATCH][STABLE] " Vitus Jensen
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=20100408172953.GG3269@jama \
--to=martin.jansa@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox