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 22:26:28 +0000	[thread overview]
Message-ID: <bug-9541-163-PNCnkTjzh7@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9541-163@https.bugs.busybox.net/>

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

--- Comment #2 from Artem Synytsyn <a.synytsyn@gmail.com> ---
Hello, Peter,

First of all I'll describe steps, which I've made.
1. Clone buildroot from official repo
2. make raspberrypi_defconfig
3. Add enc28j60.dtbo into overlays directory on boot partition
4. Add dtoverlay=enc28j60 into config.txt

After boot lsmod command output is empty(except ipv6 module, which is marked as
"permanent"). 

- I've used device tree overlay from the firmware, which was built by buildroot
itself. As for the snippet it is standard also, here is its code:
https://github.com/raspberrypi/linux/blob/rpi-4.4.y/arch/arm/boot/dts/overlays/enc28j60-overlay.dts.
Also, as I said, device tree node with this device is exposed in
/proc/device-tree, so I think it is ok.
- driver enc28j60.ko is enabled in kernel configuration as loadable, it is
present in /lib/modules filesystem. I can load it manually and it is ok too.
- mdev is present in system. And I think it is root of the problem, because
Raspbian distro has udev instead mdev and it successfully loads kernel module
based on info from device tree.

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

  parent reply	other threads:[~2016-12-30 22:26 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 ` [Buildroot] [Bug 9541] " bugzilla at busybox.net
2016-12-30 22:26 ` bugzilla at busybox.net [this message]
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-PNCnkTjzh7@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.