[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANk1AXRB4OzouKPRh2n-HfhrGGUUCh2w2BM8Zz81ZwCGU+8KCw@mail.gmail.com>
Date: Tue, 18 Jul 2017 09:32:39 -0500
From: Alan Tull <atull@...nel.org>
To: Greg KH <greg@...ah.com>
Cc: "Luebbers, Enno" <enno.luebbers@...el.com>,
Wu Hao <hao.wu@...el.com>, Moritz Fischer <mdf@...nel.org>,
linux-fpga@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-api@...r.kernel.org, "Kang, Luwei" <luwei.kang@...el.com>,
"Zhang, Yi Z" <yi.z.zhang@...el.com>,
Xiao Guangrong <guangrong.xiao@...ux.intel.com>
Subject: Re: [PATCH v2 01/22] docs: fpga: add a document for Intel FPGA driver overview
On Tue, Jul 18, 2017 at 12:22 AM, Greg KH <greg@...ah.com> wrote:
> On Mon, Jul 17, 2017 at 03:14:29PM -0500, Alan Tull wrote:
>> > Also, we're thinking that some operations require that you first "acquire
>> > ownership" of the respective device, which I believe maps more easily to
>> > open() and ioctls than sysfs.
>> >
>> > Thanks
>> > - Enno
>>
>> Yes, sysfs doesn't implement open/close so there's no clean way to
>> have one thing in userspace that owns the interface. It's a shame.
>
> No, that was by design :)
Well that's good to know! linux-api is copied on this patchset. I'm
wondering if there is another mailing list that can weigh in on this
new ioctl that is being added to the kernel or if that's the one.
Alan Tull
Powered by blists - more mailing lists