All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9541] Platform drivers autoloading from info in device tree does not work
Date: Fri, 30 Dec 2016 20:44:42 +0000	[thread overview]
Message-ID: <bug-9541-163-HsWN9ztNS7@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9541-163@https.bugs.busybox.net/>

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

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
It is hard to know what is going on without more details.

For drivers to load automatically, you need:

- Device tree snippet according to the defined bindings (in your case it sounds
like Documentation/devicetree/bindings/net/microchip,enc28j60.txt)

- Driver enabled as a module in the kernel

- A user space kernel module loader, E.G. mdev or (e)udev

If you still have problems, please provide more details about the above.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2016-12-30 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30 14:42 [Buildroot] [Bug 9541] New: Platform drivers autoloading from info in device tree does not work bugzilla at busybox.net
2016-12-30 20:44 ` bugzilla at busybox.net [this message]
2016-12-30 22:26 ` [Buildroot] [Bug 9541] " bugzilla at busybox.net
2016-12-31  8:55 ` bugzilla at busybox.net
2017-01-01 13:51 ` bugzilla at busybox.net
2017-01-02 11:03 ` 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-9541-163-HsWN9ztNS7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.