mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Matthias Klein" <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Binary patches
Date: Tue, 29 Jan 2013 13:45:36 +0000	[thread overview]
Message-ID: <em71181f5e-272d-4009-8051-8a62d23731f2@nb-mak> (raw)
In-Reply-To: <20130129131211.GA10750@regiomontanus.your-server.de>

[Bernhard Walle <bernhard@bwalle.de> 29.01.2013 14:12:11]
>Because I have the same problem I used another solution: Create a
>directory local_src/firmware, copy the binary files there and
>set in the kernel configuration
>
>   Device drivers --->
>     Generic Driver Options --->
>       [*] Include in-kernel firmware blobs in kernel binary
>           (your_firmware) External firmware blobs to build into the 
>kernel binary
>           (../../../local_src/firmware) Firmware blobs root directory
>
>That avoids the problem with binary patches.
>
>

Thank you for the tip !

But support for binary patches in ptxdist would be nice.


Best regards,

Matthias


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-01-29 13:46 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
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 [this message]
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=em71181f5e-272d-4009-8051-8a62d23731f2@nb-mak \
    --to=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