Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Picard <davepiq@yahoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] SPI module on Raspberry Pi B+
Date: Fri, 15 Jan 2016 14:06:10 +0100	[thread overview]
Message-ID: <5698EEC2.7030806@yahoo.fr> (raw)

Hello,

I just switched from Buildroot 2015.08.1 to 2015.11.1, and tried to keep 
the same configuration. SPI was working well, before the switch.

Now, I am having some trouble with the SPI driver, namely spi_bcm2835 : 
when I insert the module, there is no log in dmesg output, and nothing 
is created in /sys/bus/spi/devices.

I could make it work by loading spi_bcm2708 instead, despite the 
deprecated warning. In this case, I get some logging messages and 
/sys/bus/spi/devices/spi0.0 and /sys/bus/spi/devices/spi0.1 appear.

Any idea ?

David.

------------------
Board : Raspberry Pi B+
Buildroot : 2015.11.1
SPI peripheral : Adafruit PiTFT 2.8"

             reply	other threads:[~2016-01-15 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 13:06 David Picard [this message]
2016-01-15 21:35 ` [Buildroot] SPI module on Raspberry Pi B+ Peter Seiderer
  -- strict thread matches above, loose matches on Subject: below --
2016-01-15 13:08 David Picard

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=5698EEC2.7030806@yahoo.fr \
    --to=davepiq@yahoo.fr \
    --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