Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: update-alternatives and kernel modules
Date: Tue, 12 Mar 2013 17:32:23 -0500	[thread overview]
Message-ID: <513FACF7.5000907@windriver.com> (raw)

I have someone who is trying to use update-alternatives with kernel modules.

They discovered that the rename code changes the name of the module to end in 
.ko.${BPN}.  While the package.bbclass code specifically looks for the file name 
to end in '.ko' in order to avoid stripping the modules... so of course the 
modules get stripped and no longer work properly.

So my question is, is it even reasonable to use update-alternatives with kernel 
modules?  If it is, we probably need to change the trigger in packages.bbclass 
to look for either .ko or .ko.${BPN} (or something similar).

Any comments/suggestions?
--Mark



             reply	other threads:[~2013-03-12 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 22:32 Mark Hatle [this message]
2013-03-13 13:07 ` update-alternatives and kernel modules Bruce Ashfield
2013-03-13 13:35   ` Mark Hatle
2013-03-13 13:48     ` Martin Jansa
2013-03-13 15:05       ` Mark Hatle

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=513FACF7.5000907@windriver.com \
    --to=mark.hatle@windriver.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