From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [patch] ti-cs1-omap3530 upgrade
Date: Thu, 05 Nov 2009 16:27:03 +0100 [thread overview]
Message-ID: <hcuqs7$elg$1@ger.gmane.org> (raw)
In-Reply-To: <afb7987a0911040032g2bebec62j70a81dd409561c17@mail.gmail.com>
Hello Andrea,
Thank you for you patch! Could you send it in git-format-patch format so
we can properly attribute it to you?
regards,
Koen
On 04-11-09 09:32, Andrea wrote:
> Is possible upgrade cs1-omap3530?
> thank you
> Andrea Seraghiti
>
> diff --git a/recipes/ti/ti-cs1-omap3530_1.0.1.bb
> b/recipes/ti/ti-cs1-omap3530_1.0.1.bb
> index 9779c33..039aa92 100644
> --- a/recipes/ti/ti-cs1-omap3530_1.0.1.bb
> +++ b/recipes/ti/ti-cs1-omap3530_1.0.1.bb
> @@ -1,12 +1,12 @@
> require ti-codec.inc
> require ti-cs1-omap3530.inc
>
> -SRC_URI =
> "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_00/latest//exports/cs1omap3530_setuplinux_1_00_01-42.bin"
> +SRC_URI =
> "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_00/latest//exports/cs1omap3530_setuplinux_1_00_01-44.bin"
>
> # Specify names of the InstallJammer binary file and the tarball it extracts
> -BINFILE = "cs1omap3530_setuplinux_1_00_01-42.bin"
> +BINFILE = "cs1omap3530_setuplinux_1_00_01-44.bin"
>
> -S = "${WORKDIR}/dvsdk_3_00_01_42/cs1omap3530_1_00_01"
> +S = "${WORKDIR}/dvsdk_3_00_02_44/cs1omap3530_1_00_01"
>
> DEPENDS="ti-codec-engine ti-dsplink-module"
>
>
>
>
> diff --git a/conf/checksums.ini b/conf/checksums.ini
> index a2d7bda..d5a9944 100644
> --- a/conf/checksums.ini
> +++ b/conf/checksums.ini
> @@ -4486,6 +4486,10 @@
> sha256=8b718c344cf19417447cbc16867d2e04434654c13b330598b96720ead146b961
> md5=0aa2f94c39123f1a0352983e5366179c
> sha256=4bab529afa00cafde3bc5df2769578c88438f80c5152d4257cd0e86986f95bc4
>
> +[http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_00/latest//exports/cs1omap3530_setuplinux_1_00_01-44.bin]
> +md5=4db567252e6c43119e1c0aafe401a679
> +sha256=e042e1aad42a6728adf5c955dc38e4f8331fc0eacd833f1cd75d9cbb4faff0b5
> +
> [http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_00/latest//exports/cs1omap3530_setuplinux_1_00_01-42.bin]
> md5=a1e19ef37638e977d059fd22af666301
> sha256=fc7ac2829df8d394635aa1cc704b78e93ca287111df1001e5738ae2282691219
next prev parent reply other threads:[~2009-11-05 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 8:32 [patch] ti-cs1-omap3530 upgrade Andrea
2009-11-05 15:27 ` Koen Kooi [this message]
2009-11-06 10:25 ` Andrea
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='hcuqs7$elg$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.