From: Moritz Fischer <email@example.com> To: Jason Gunthorpe <firstname.lastname@example.org> Cc: Alan Tull <email@example.com>, firstname.lastname@example.org, linux-kernel <email@example.com>, firstname.lastname@example.org Subject: Re: [RFC 7/8] fpga-region: add sysfs interface Date: Thu, 16 Feb 2017 10:11:49 -0800 [thread overview] Message-ID: <CAAtXAHdy+0A3+r2HtSXgupBG60cji2cFQ_ynnX4dGhMb+x1vgQ@mail.gmail.com> (raw) In-Reply-To: <20170216175621.GB17067@obsidianresearch.com> On Thu, Feb 16, 2017 at 9:56 AM, Jason Gunthorpe <email@example.com> wrote: > On Thu, Feb 16, 2017 at 11:47:08AM -0600, Alan Tull wrote: > >> > Just to clarify: I was proposing using the binary format of dts, >> > not actually requiring devicetree for it to work. There's plenty >> > of people running u-boot on x86 using FIT images to boot. >> >> The FPGA images should not be required to have OS specific parts. >> Some ahem non-Linux OS's that use FPGAs don't use device tree, so that >> adds an extra complication for them unnecessarily. That's a good point, I had assumed that pulling in a C library shouldn't be an issue for any OS (u-boot can do it, BSD can do it, Linux can do it). I have to admit I didn't think about Windows :) > Not just that, but we parse the bitfile headers in user space as well. > > Requiring people to use libfdt pretty much kills the idea because of > its GPL license. <snip> libfdt, however, is GPL/BSD dual-licensed. That is, it may be used either under the terms of the GPL, or under the terms of the 2-clause BSD license (aka the ISC license). The full terms of that license are given in the copyright banners of each of the libfdt source files. This is, in practice, equivalent to being BSD licensed, since the terms of the BSD license are strictly more permissive than the GPL. </snip> > As I've shown the plain text headers can be produced in a scripting > langauge, and are trivially consumed without much trouble. IHMO this > makes it more likely there would be adoption.. If you provide a reasonably well documented format and make your tools easy to use and integrate, I don't think that would be an issue. I was really mainly concerned about the parsing userspace provided strings in kernel being a security issue. If everyone else feels http style plain text is the best we can do, so be it. I wanted to look around and see how far I get with fdt, but anyway I'm quite busy with other work at the moment. If someone comes around and writes code that we can review, maybe that's better than not having a solution. I'll see how far I get, maybe it turns out my proposal is a bad idea anyways once I start writing actual code :) Moritz
next prev parent reply other threads:[~2017-02-16 18:11 UTC|newest] Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-15 16:14 FPGA Region enhancements and fixes Alan Tull 2017-02-15 16:14 ` [RFC 1/8] fpga-mgr: add a single function for fpga loading methods Alan Tull 2017-02-16 0:36 ` matthew.gerlach 2017-02-15 16:14 ` [RFC 2/8] fpga-region: support more than one overlay per FPGA region Alan Tull 2017-02-16 16:50 ` matthew.gerlach 2017-02-16 17:35 ` Alan Tull 2017-02-15 16:14 ` [RFC 3/8] fpga-bridge: add non-dt support Alan Tull 2017-02-15 16:14 ` [RFC 4/8] doc: fpga-mgr: separate getting/locking FPGA manager Alan Tull 2017-02-17 17:14 ` Li, Yi 2017-02-17 21:55 ` Alan Tull 2017-02-17 17:52 ` Moritz Fischer 2017-02-17 22:02 ` Alan Tull 2017-02-15 16:14 ` [RFC 5/8] " Alan Tull 2017-02-15 16:14 ` [RFC 6/8] fpga-region: separate out common code to allow non-dt support Alan Tull 2017-02-15 16:14 ` [RFC 7/8] fpga-region: add sysfs interface Alan Tull 2017-02-15 17:21 ` Jason Gunthorpe 2017-02-15 17:46 ` Alan Tull 2017-02-15 17:55 ` Moritz Fischer 2017-02-15 18:06 ` Jason Gunthorpe 2017-02-15 18:23 ` Alan Tull 2017-02-15 18:31 ` Moritz Fischer 2017-02-15 19:49 ` Jason Gunthorpe 2017-02-15 22:49 ` Alan Tull 2017-02-15 23:07 ` Jason Gunthorpe 2017-02-15 20:07 ` matthew.gerlach 2017-02-15 20:37 ` Jason Gunthorpe 2017-02-15 20:54 ` Moritz Fischer 2017-02-15 21:15 ` Jason Gunthorpe 2017-02-15 21:36 ` Moritz Fischer 2017-02-15 22:42 ` Alan Tull 2017-02-16 0:16 ` Moritz Fischer 2017-02-16 17:47 ` Alan Tull 2017-02-16 17:56 ` Jason Gunthorpe 2017-02-16 18:11 ` Moritz Fischer [this message] 2017-02-17 22:28 ` Yves Vandervennet 2017-02-18 2:30 ` Moritz Fischer 2017-02-18 12:45 ` Nadathur, Sundar 2017-02-18 20:10 ` Alan Tull 2017-02-18 20:45 ` Moritz Fischer 2017-02-19 15:00 ` Alan Tull 2017-02-19 23:16 ` Alan Tull 2017-02-20 23:49 ` Moritz Fischer 2017-02-21 18:33 ` Alan Tull 2017-02-22 3:13 ` Nadathur, Sundar 2017-02-22 3:49 ` Moritz Fischer 2017-02-22 5:12 ` Jason Gunthorpe 2017-02-22 5:38 ` Moritz Fischer 2017-02-22 5:46 ` Nadathur, Sundar 2017-02-22 6:05 ` Moritz Fischer 2017-02-22 16:44 ` Jason Gunthorpe 2017-02-22 17:50 ` Moritz Fischer 2017-02-22 17:54 ` Jason Gunthorpe 2017-02-22 17:57 ` Moritz Fischer 2017-02-22 16:33 ` Alan Tull 2017-02-22 16:44 ` Moritz Fischer 2017-02-22 16:52 ` Alan Tull 2017-02-27 20:09 ` Alan Tull 2017-02-27 22:49 ` Moritz Fischer 2017-02-28 0:04 ` matthew.gerlach 2017-02-15 21:20 ` Anatolij Gustschin 2017-02-15 16:14 ` [RFC 8/8] doc: fpga: add sysfs document for fpga region Alan Tull 2017-02-28 17:35 ` FPGA Region enhancements and fixes Alan Tull 2017-02-28 22:03 ` Alan Tull
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=CAAtXAHdy+0A3+r2HtSXgupBG60cji2cFQ_ynnX4dGhMb+x1vgQ@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC 7/8] fpga-region: add sysfs interface' \ /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
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.