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: Mon, 28 Jan 2013 16:06:36 +0100	[thread overview]
Message-ID: <510693FC.9070503@corscience.de> (raw)
In-Reply-To: <em0200ce1f-6bac-44e9-bd6e-7450e135e1fe@nb-mak>

Hi Matthias,

please do not top post full quote.

On 28.01.2013 15:38, Matthias Klein wrote:
> Hi Andreas,
> 
> my intension is to create a patch file (containing the firmware) which
> will be applied at the kernel.prepare step using the series file.

Well, as I thought, so please try my step by step guide.

And to be exact the patches will be applied in the extract phase. The
prepare phase will call the configure stuff for the respective package
you build.

> (Then at the kernel.compile step the firmware should be compiled into
> the kernel.)

That is why we need the patches ;)

Best regards

Andreas Bießmann


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-01-28 15:06 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 [this message]
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
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=510693FC.9070503@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