From: Mike Marciniszyn <mike.marciniszyn@intel.com>
To: mmarek@suse.cz
Cc: Doug Ledford <dledford@redhat.com>,
linux-kbuild@vger.kernel.org, mmarcini@yahoo.com
Subject: [PATCH 2/3] kbuilld: install firmware files in kernel relative directory
Date: Mon, 24 Jun 2013 10:38:28 -0400 [thread overview]
Message-ID: <20130624143828.10761.20718.stgit@phlsvslse11.ph.intel.com> (raw)
In-Reply-To: <20130624143658.10761.3787.stgit@phlsvslse11.ph.intel.com>
Prior to this patch, firmware files were being installed
in /lib/firmware with a potential conflict with already
installed kernels.
firmware files are now installed in /lib/firmware/<release>
and packaged with the rest of the modules.
Signed-off-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
---
scripts/package/mkspec | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/scripts/package/mkspec b/scripts/package/mkspec
index 0aa6a24..514aeb2 100755
--- a/scripts/package/mkspec
+++ b/scripts/package/mkspec
@@ -77,13 +77,14 @@ echo "%install"
echo 'KBUILD_IMAGE=$(make image_name)'
echo "%ifarch ia64"
echo 'mkdir -p $RPM_BUILD_ROOT/boot/efi $RPM_BUILD_ROOT/lib/modules'
-echo 'mkdir -p $RPM_BUILD_ROOT/lib/firmware'
echo "%else"
echo 'mkdir -p $RPM_BUILD_ROOT/boot $RPM_BUILD_ROOT/lib/modules'
-echo 'mkdir -p $RPM_BUILD_ROOT/lib/firmware'
echo "%endif"
+echo 'mkdir -p $RPM_BUILD_ROOT'"/lib/firmware/$KERNELRELEASE"
-echo 'INSTALL_MOD_PATH=$RPM_BUILD_ROOT make %{?_smp_mflags} KBUILD_SRC= modules_install'
+echo 'INSTALL_MOD_PATH=$RPM_BUILD_ROOT make %{?_smp_mflags} KBUILD_SRC= mod-fw= modules_install'
+echo 'INSTALL_FW_PATH=$RPM_BUILD_ROOT'"/lib/firmware/$KERNELRELEASE"
+echo 'make INSTALL_FW_PATH=$INSTALL_FW_PATH' firmware_install
echo "%ifarch ia64"
echo 'cp $KBUILD_IMAGE $RPM_BUILD_ROOT'"/boot/efi/vmlinuz-$KERNELRELEASE"
echo 'ln -s '"efi/vmlinuz-$KERNELRELEASE" '$RPM_BUILD_ROOT'"/boot/"
@@ -125,7 +126,7 @@ echo "%files"
echo '%defattr (-, root, root)'
echo "%dir /lib/modules"
echo "/lib/modules/$KERNELRELEASE"
-echo "/lib/firmware"
+echo "/lib/firmware/$KERNELRELEASE"
echo "/boot/*"
echo ""
echo "%files headers"
next prev parent reply other threads:[~2013-06-24 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 14:38 [PATCH 0/3] RPM enhancements for kbuild Mike Marciniszyn
2013-06-24 14:38 ` [PATCH 1/3] kbuild: add %post section to create initramfs and grub hooks Mike Marciniszyn
2013-07-23 13:19 ` Michal Marek
2013-06-24 14:38 ` Mike Marciniszyn [this message]
2013-07-23 13:19 ` [PATCH 2/3] kbuilld: install firmware files in kernel relative directory Michal Marek
2013-06-24 14:38 ` [PATCH 3/3] kbuild: add generation of kernel-devel Mike Marciniszyn
2013-07-04 15:15 ` Michal Marek
2013-07-05 13:04 ` Marciniszyn, Mike
2013-07-05 20:29 ` Michal Marek
2013-07-05 13:12 ` Marciniszyn, Mike
2013-07-05 13:17 ` Marciniszyn, Mike
2013-07-05 20:30 ` Michal Marek
2013-07-08 11:55 ` Marciniszyn, Mike
2013-07-08 12:12 ` Michal Marek
2013-07-08 13:15 ` Marciniszyn, Mike
2013-07-08 13:32 ` Doug Ledford
2013-07-08 13:39 ` Marciniszyn, Mike
2013-07-08 14:45 ` Michal Marek
2013-07-08 15:52 ` Marciniszyn, Mike
2013-07-08 16:20 ` Doug Ledford
2013-07-08 17:17 ` Marciniszyn, Mike
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=20130624143828.10761.20718.stgit@phlsvslse11.ph.intel.com \
--to=mike.marciniszyn@intel.com \
--cc=dledford@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarcini@yahoo.com \
--cc=mmarek@suse.cz \
/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