Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1436845

Re: portable device tree connector -- problem statement

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Jul 04, 2016 at 01:58:53PM -0700, Frank Rowand wrote:

> On the other hand, I have no previous detailed knowledge of the beagle
> family.

This is in no way specific to the BeagleBones, there's plenty of other
boards out there with similar setups like the Raspberry Pi and its
derivatives.  

>     - for bones with the same pinout:
>       - the pins are routed to different function blocks on the
>         SOC because different bones may have different SOCs?
>         - the different functional blocks are compatible or not?

This is the general case, there will be a substantial level of
compatibility between different base boards by virtue of the pinouts
being the same but obviously there will be some variation in the
specifics (and even where that exists it may not be enough to be visible
at the DT level for the most part).  That said there will doubtless be
some plug in modules that want to rely on the specifics of a given base
board rather than remain compatible with general users of the interface.

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

portable device tree connector -- problem statement Frank Rowand <frowand.list@gmail.com> - 2016-07-04 23:00 +0200
  Re: portable device tree connector -- problem statement Mark Brown <broonie@kernel.org> - 2016-07-05 10:40 +0200
    Re: portable device tree connector -- problem statement Frank Rowand <frowand.list@gmail.com> - 2016-07-05 16:30 +0200
      Re: portable device tree connector -- problem statement Pantelis Antoniou <pantelis.antoniou@konsulko.com> - 2016-07-05 20:10 +0200
    Re: portable device tree connector -- problem statement Pantelis Antoniou <pantelis.antoniou@konsulko.com> - 2016-07-05 20:10 +0200

csiph-web