devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Federico Vaga <federico.vaga-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Walter Goossens <waltergoossens-CmkmPbn3yAE@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: DeviceTree FPGA bitstream
Date: Mon, 15 Jun 2015 10:55:46 +0200	[thread overview]
Message-ID: <20150615085546.GA19162@pcbe13110.cern.ch> (raw)
In-Reply-To: <55796021.7010402-CmkmPbn3yAE@public.gmane.org>

Hi Walter,

On Thu, Jun 11, 2015 at 12:17:05PM +0200, Walter Goossens wrote:
> On 06/09/2015 04:49 PM, Federico Vaga wrote:
>> - it looks like the DeviceTree is disable for x86 architecture except for
>> some specific platform. Is it possible to enable it for the entire x86
>> architecture? Are there any reason to disable it by default?
>>
>> - I read that since versione 3.17 it should be possible to dynamically
>> add
>> portion of DeviceTree from configfs. Is it possible on all architecture?
>>
>> - I'm working on x86_64 and my FPGA can be on a pluggable board (e.g.
>> PCIe).
>> Is there a way to describe this situation with DeviceTree? Is there
>> any tool
>> that dynamically computes the addresses (interrupts) translation to use
>> (e.g. on PCIe) ?
>>
>
> I've been using this scheme on PPC for quite some time (before
> devicetree overlays) by creating a custom pcie driver (that knows the
> bar addresses and irqs) which then instantiates a "virtual platformbus"
> at the pcie bar the fpga is located in.
> You can adopt this scheme for x86 by creating a bus and using the
> devicetree code to probe the inside of your FPGA but this is all a bit
> hackish.
> The correct approach (in my opinion) would be to use an overlay
> describing the contents of the FPGA and loading that when probing the
> pcie-device.

This is more or less what I thought

> This would however require a base devicetree to apply the
> overlay to, and I'm not sure how much effort this is going to be on x86_64

Not sure but I fear that is not enough to make it stable. The compilation of
the DeviceTree is allowed only on x86 and on some specific platform.

Of course, I can modify the Kconfig to allow the compilation of the
DeviceTree but then I don't know if it will work and how it will work.
I mean are there particular reasons to keep the DeviceTree away from x86 ?
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2015-06-15  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 14:49 DeviceTree FPGA bitstream Federico Vaga
     [not found] ` <20150609144901.GC12677-cpfkIQmgKd5FPxEMnUtzR+1GAupnlqi7@public.gmane.org>
2015-06-11 10:17   ` Walter Goossens
     [not found]     ` <55796021.7010402-CmkmPbn3yAE@public.gmane.org>
2015-06-15  8:55       ` Federico Vaga [this message]

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=20150615085546.GA19162@pcbe13110.cern.ch \
    --to=federico.vaga-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=waltergoossens-CmkmPbn3yAE@public.gmane.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).