Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8346] New: wf111 package removes all kernel module dependencies
Date: Thu, 17 Sep 2015 16:11:31 +0000 (UTC)	[thread overview]
Message-ID: <bug-8346-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=8346

           Summary: wf111 package removes all kernel module dependencies
           Product: buildroot
           Version: 2015.05
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: mstarr at hedonline.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 6161
  --> https://bugs.busybox.net/attachment.cgi?id=6161
Patch to fix wf111 overwriting module files during install

If the wf111 package is selected and the source is given, the package builds
and runs depmod in its output directory.  Then in the install target the
contents of the output directory are copied to the target/lib/modules/<VERSION>
directory.  When the install step occurs the module.* files are overwritten
with the wf111 files resulting in only the wf111 driver kernel module showing
up on the target.

This is detected by running "modprobe -l" on the target hardware and it will
only show the extra/unifi_sdio.ko kernel module.  This prevents loading of any
other kernel modules enabled in the kernel configuration.

As a solution the WF111_INSTALL_CMDS is removed and under the WF111_BUILD_CMDS,
 the following can be added to the make command:
OUTPUT=$(TARGET_DIR).

This points the build to install to the target directory and not the local
output directory.  This in turn catches all the other kernel modules when
depmod is run.  The only issue with this is that under the build target of
wf111, it will also be installing the software too which is usually handled
under the install target.

Attached is a patch that makes the changes suggested above.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2015-09-17 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 16:11 bugzilla at busybox.net [this message]
2015-12-01 21:41 ` [Buildroot] [Bug 8346] wf111 package removes all kernel module dependencies bugzilla at busybox.net
2015-12-01 21:45 ` bugzilla at busybox.net
2016-04-25 22:05 ` bugzilla at busybox.net

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=bug-8346-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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