From: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
To: Openembedded Core <openembedded-core@lists.openembedded.org>
Subject: Avoid stripping of firmware files?
Date: Thu, 26 Jan 2012 14:00:58 +0100 [thread overview]
Message-ID: <4F214E8A.4030209@ts.fujitsu.com> (raw)
Hi,
for my work on the dm8148-evm I got firmware files with the suffix
".xem3" from TI. I made a simple recipe to install those files in my
image, but I ran into a bad problem:
The firmware files I find in my image are different from the files i use
in my recipe. No matter if I use "install" or just "cp" to copy the
files to the destination.
Looks like those files get stripped during packaging. Normally not a bad
idea, but in this special case stripping the symbols makes the files
dysfunctional.
Is there a way to avoid stripping?
Regards
Rainer
--
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE
Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany
Telephone: +49-821-804-3321
Telefax: +49-821-804-2131
Mail: mailto:Rainer.Koenig@ts.fujitsu.com
Internet ts.fujtsu.com
Company Details ts.fujitsu.com/imprint.html
next reply other threads:[~2012-01-26 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 13:00 Rainer Koenig [this message]
2012-01-26 13:55 ` Avoid stripping of firmware files? Richard Purdie
2012-01-26 14:37 ` Rainer Koenig
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=4F214E8A.4030209@ts.fujitsu.com \
--to=rainer.koenig@ts.fujitsu.com \
--cc=openembedded-core@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