From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9541] New: Platform drivers autoloading from info in device tree does not work
Date: Fri, 30 Dec 2016 14:42:34 +0000 [thread overview]
Message-ID: <bug-9541-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9541
Bug ID: 9541
Summary: Platform drivers autoloading from info in device tree
does not work
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: a.synytsyn at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Hello everyone! What is going on with autoloading modules for platform devices
from device tree? I've build image for raspberry pi, added device tree overlay
for enc28j60. I've checked: device tree node with this device exists in
/proc/device-tree/soc/spi at 7e204000. But lsmod does not shows that enc28j60.ko
is not loaded. In contrast of, raspbian distro successfully managed with this -
module loaded successfully.
Also, I've read this thread:
http://lists.busybox.net/pipermail/buildroot/2016-December/178779.html. As I
understand, command
find /sys/ -name modalias -print0 | xargs -0 sort -u -z | xargs -0
modprobe -abq
does not work.
Regards,
Artem Synytsyn
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-12-30 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 14:42 bugzilla at busybox.net [this message]
2016-12-30 20:44 ` [Buildroot] [Bug 9541] Platform drivers autoloading from info in device tree does not work bugzilla at busybox.net
2016-12-30 22:26 ` 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@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