From: vladoman@gmail.com (Vladimir Pantelic)
To: linux-arm-kernel@lists.infradead.org
Subject: Unifying cape overlays into boot .dtb for BeagleBoard.org boards
Date: Tue, 17 Jun 2014 15:45:59 +0200 [thread overview]
Message-ID: <53A04697.1020904@gmail.com> (raw)
In-Reply-To: <20140617090931.GB3705@n2100.arm.linux.org.uk>
On 06/17/2014 11:09 AM, Russell King - ARM Linux wrote:
> Here's the most obvious question in the world on this topic. Are capes
> hot-pluggable?
"capes" as in Beaglebone capes might not be due to the mechanical
constraints you listed.
"capes" as a concept of pluggable hardware might well be. here is a real
world example of commercially available pluggable hardware add-ons on a
Linux system back from 2008:
http://en.wikipedia.org/wiki/Archos_Generation_6#Accessories
depending on the add-on, different interfaces like GPIO, UART, USB, SPI
using the same pins were used and there was no reboot needed to load a
new hardware configuration or change the pinmux
next prev parent reply other threads:[~2014-06-17 13:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+T6QP==raXdWz9mezK3JxSvZjWhUZZ7aKv4CpCr0SbdaCMgDQ@mail.gmail.com>
2014-06-11 5:11 ` Unifying cape overlays into boot .dtb for BeagleBoard.org boards Jason Kridner
2014-06-17 7:11 ` Gupta, Pekon
2014-06-17 16:25 ` Jason Kridner
2014-06-18 8:51 ` Gupta, Pekon
2014-06-26 7:50 ` Tony Lindgren
2014-06-26 13:06 ` Tom Rini
2014-06-26 15:27 ` Jason Kridner
2014-06-16 13:22 ` Jason Kridner
2014-06-17 9:09 ` Russell King - ARM Linux
2014-06-17 12:37 ` Tom Rini
2014-06-17 12:56 ` Russell King - ARM Linux
2014-06-17 14:58 ` Tom Rini
2014-06-17 12:58 ` Matt Porter
2014-06-17 13:15 ` Russell King - ARM Linux
2014-06-17 13:30 ` Matt Porter
2014-06-17 13:32 ` Pantelis Antoniou
2014-06-17 16:01 ` Russell King - ARM Linux
2014-06-17 16:33 ` Jason Kridner
2014-06-17 16:59 ` Pantelis Antoniou
2014-06-17 17:05 ` Russell King - ARM Linux
2014-06-17 17:10 ` Pantelis Antoniou
2014-06-17 17:41 ` Russell King - ARM Linux
2014-06-17 19:24 ` Pantelis Antoniou
2014-06-17 13:45 ` Vladimir Pantelic [this message]
2014-06-17 13:50 ` Grant Likely
2014-06-17 14:08 ` Iain Paton
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=53A04697.1020904@gmail.com \
--to=vladoman@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).