All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Ellis <scott@jumpnowtek.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-2017.11.1 and cape manager for Beaglebone Black.
Date: Tue, 20 Feb 2018 08:09:06 -0500 (EST)	[thread overview]
Message-ID: <1519132146.05324245@apps.rackspace.com> (raw)


You don't need cape manager for the built-in CAN controllers of the BBB
or to use any CAN capes with external CAN controllers that the BBB
communicates with over SPI.
 
It's just a matter of adding some sections to your dts. You can do it with
an include to your main dts.
 
Here are some links for dts includes to the 4.4 mainline kernel to enable
the built-in CAN controllers. Just a little pin muxing. This assumes you
have the kernel modules enabled, which you probably do.
 
The cape manager stuff was never supported by mainline linux or even TI
linux kernels only the Beaglebone specific kernels. And it's not even
supported by the Beagleboard folks anymore.They have moved to a u-boot
approach.
 
Cape manager is a technological dead-end.
 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180220/48c986f4/attachment.html>

             reply	other threads:[~2018-02-20 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 13:09 Scott Ellis [this message]
2018-02-21 10:35 ` [Buildroot] buildroot-2017.11.1 and cape manager for Beaglebone Black carlos at fgh.co.uk
  -- strict thread matches above, loose matches on Subject: below --
2018-02-20 11:34 carlos at fgh.co.uk

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=1519132146.05324245@apps.rackspace.com \
    --to=scott@jumpnowtek.com \
    --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.