mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.biessmann@corscience.de>
To: ptxdist@pengutronix.de, Matthias Klein <matthias.klein@optimeas.de>
Subject: Re: [ptxdist] Binary patches
Date: Tue, 29 Jan 2013 10:58:46 +0100	[thread overview]
Message-ID: <51079D56.7040301@corscience.de> (raw)
In-Reply-To: <eme72652d1-eb38-4e4a-8009-f8c8ba9c9be4@nb-mak>

Hi Matthias,

On 29.01.2013 09:39, Matthias Klein wrote:
> Hi Andreas,
> 
>> Well, as I thought, so please try my step by step guide.
>>
> Sorry, at the first reading I have your step guide.
> 
> 
> I have followed your step guide, and git creates a now patch file in the
> format you described (GIT binary patch) and added it to the series file.
> Very nice. Is the "extract --git" and "git ptx-patches" somewhere
> documented?

I do not know if this made it into the 'How to become a PTXdist Guru'
document. I got this hint by Michael last year:
http://article.gmane.org/gmane.comp.embedded.ptxdist.devel/8544

> But then at the normal "extract" I get a error from patch:
> 
> applying '0050-SDMA-firmware.patch'
> patch: **** Only garbage was found in the patch input.
> make: *** [.../platform-tx53/state/kernel.extract] Error 2
> 
> Do I make something wrong, or do I need a speacial "patch" version for
> GIT binary patches?
Not that I know of, patch 2.6.1 works for me here as expected (Debian
Wheezy):

---8<---
0078-add-binary-blob.patch
patchin: git: done

finished target kernel.extract
./p_normal extract kernel  29,22s user 7,69s system 74% cpu 49,745 total
abiessmann@azuregos % git --version
git version 1.7.10.4
abiessmann@azuregos % patch --version
patch 2.6.1
abiessmann@azuregos % ls -la
platform-test/build-target/linux-3.4/firmware/CKFA.bin
-rwxr-xr-x 1 abiessmann abiessmann 6668 Jan 29 10:25
platform-test/build-target/linux-3.4/firmware/CKFA.bin*
abiessmann@azuregos % head -20 patches/linux-3.4/0078-add-binary-blob.patch
From: =?UTF-8?q?Andreas=20Bie=C3=9Fmann?= <andreas.biessmann@corscience.de>
Date: Tue, 29 Jan 2013 10:24:15 +0100
Subject: [PATCH] add binary blob
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Andreas Bießmann <andreas.biessmann@corscience.de>
---
 firmware/CKFA.bin |  Bin 0 -> 6668 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100755 firmware/CKFA.bin

diff --git a/firmware/CKFA.bin b/firmware/CKFA.bin
new file mode 100755
index
0000000000000000000000000000000000000000..9befbf415a9fd8bcc19655ca1dc50966d248ebba
GIT binary patch
literal 6668
zcmbtZ3w)DBwx91y`ZfLf<Y`}~vGPa>FOhY<B9MGZ)AUJ+H4EN?Jo-okn_eCttS?$9
zP*ODI0|OKva4nDz*5!(Ny{v*D0akgat6r8xmSq*uYqIFtE&`Ho&zU5oRFwO>H~CG@
--->8---

Beside that, have you thought about Roberts comment?
You can not distribute binary BLOB in a GPLv2 software and refuse
disclosure of that blob. To load binary closed source firmware blobs the
linux kernel provides a userspace interface. You should use that if you
intend to sell this device.

Best regards

Andreas Bießmann

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-01-29  9:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 10:54 Matthias Klein
2013-01-28 13:19 ` Matthias Klein
2013-01-28 14:31   ` Andreas Bießmann
2013-01-28 14:38     ` Matthias Klein
2013-01-28 15:06       ` Andreas Bießmann
2013-01-29  8:39         ` Matthias Klein
2013-01-29  9:58           ` Andreas Bießmann [this message]
2013-01-29 10:20             ` Juergen Beisert
2013-01-29 10:26               ` Matthias Klein
2013-01-29 11:12                 ` Andreas Bießmann
2013-01-29 12:06                   ` Bernhard Walle
2013-01-29 12:30                     ` Bernhard Walle
2013-01-29 13:29                       ` Andreas Bießmann
2013-01-29 13:40                         ` Bernhard Walle
2013-01-29 10:29               ` Bernhard Walle
2013-01-28 19:14       ` Robert Schwebel
2013-01-29 13:12       ` Bernhard Walle
2013-01-29 13:45         ` Matthias Klein
2013-01-31 10:32     ` Alexander Stein

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=51079D56.7040301@corscience.de \
    --to=andreas.biessmann@corscience.de \
    --cc=matthias.klein@optimeas.de \
    --cc=ptxdist@pengutronix.de \
    /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