On Sat, 6 Dec 2014, Grant Likely wrote:
> >> +int fpga_mgr_write(struct fpga_manager *mgr, const char *buf, size_t
> >> count)
> >> +{
> >> + int ret;
> >> +
> >> + if (test_and_set_bit_lock(FPGA_MGR_BUSY, &mgr->flags))
> >> + return -EBUSY;
> >> +
> >> + dev_info(mgr->dev
Hi!
> > * this causes the fpga to get programmed
> > * appropriate bridges get enabled
> > * appropriate drivers get probed
>
> For the case of a fixed function device it's sort of equivalent to a
> firmware load (in fact it *is* just a firmware load). The fixed function
> cases don't actually ev
On Tue, 9 Dec 2014, One Thousand Gnomes wrote:
Hi Alan,
> > I agree with the view that a FPGA is something that can get reprogrammed a
> > lot.
> > That's a flexibility we want to use. I don't see a problem with using
> > firmware
> > to do the programming as long as we have a lightweight inte
> I agree with the view that a FPGA is something that can get reprogrammed a
> lot.
> That's a flexibility we want to use. I don't see a problem with using
> firmware
> to do the programming as long as we have a lightweight interface where we can
> load an image, use it, then later reset the FGP
On Mon, 8 Dec 2014, One Thousand Gnomes wrote:
> On Sat, 6 Dec 2014 13:00:17 +
> Grant Likely wrote:
>
> > On Fri, Oct 24, 2014 at 11:52 AM, Pavel Machek wrote:
> > > Hi!
> > >
> > >> * /sys/class/fpga_manager//firmware
> > >> Name of FPGA image file to load using firmware class.
> > >>
On 12/09/2014 02:11 PM, Grant Likely wrote:
> On Mon, Dec 8, 2014 at 10:55 PM, One Thousand Gnomes
> wrote:
>> On Sat, 6 Dec 2014 13:00:17 +
>> Grant Likely wrote:
>>
>>> On Fri, Oct 24, 2014 at 11:52 AM, Pavel Machek wrote:
Hi!
> * /sys/class/fpga_manager//firmware
> Nam
On Mon, Dec 8, 2014 at 10:55 PM, One Thousand Gnomes
wrote:
> On Sat, 6 Dec 2014 13:00:17 +
> Grant Likely wrote:
>
>> On Fri, Oct 24, 2014 at 11:52 AM, Pavel Machek wrote:
>> > Hi!
>> >
>> >> * /sys/class/fpga_manager//firmware
>> >> Name of FPGA image file to load using firmware class.
>
On Sat, 6 Dec 2014 13:00:17 +
Grant Likely wrote:
> On Fri, Oct 24, 2014 at 11:52 AM, Pavel Machek wrote:
> > Hi!
> >
> >> * /sys/class/fpga_manager//firmware
> >> Name of FPGA image file to load using firmware class.
> >> $ echo image.rbf > /sys/class/fpga_manager//firmware
> >
> > I ..
On 12/08/2014 11:50 AM, Grant Likely wrote:
> On Sat, 6 Dec 2014 14:55:33 +0100
> , Pavel Machek
> wrote:
>> Hi!
>>
I am accustomed to doing 'echo -n' for most of sysfs anyway. Once in a
while I am a bonehead and forget the '-n' and spend a few minutes
wondering why this thing t
On Mon, Dec 8, 2014 at 5:56 PM, Pantelis Antoniou
wrote:
> Hi Grant,
>
>> On Dec 8, 2014, at 19:50 , Grant Likely wrote:
>>
>> On Sat, 6 Dec 2014 14:55:33 +0100
>> , Pavel Machek
>> wrote:
>>> Hi!
>>>
> I am accustomed to doing 'echo -n' for most of sysfs anyway. Once in a
> while I am
On Mon, Dec 8, 2014 at 5:50 PM, Grant Likely wrote:
> On Sat, 6 Dec 2014 14:55:33 +0100
> , Pavel Machek
> wrote:
>> Hi!
>>
>> > > I am accustomed to doing 'echo -n' for most of sysfs anyway. Once in a
>> > > while I am a bonehead and forget the '-n' and spend a few minutes
>> > > wondering why
Hi Grant,
> On Dec 8, 2014, at 19:50 , Grant Likely wrote:
>
> On Sat, 6 Dec 2014 14:55:33 +0100
> , Pavel Machek
> wrote:
>> Hi!
>>
I am accustomed to doing 'echo -n' for most of sysfs anyway. Once in a
while I am a bonehead and forget the '-n' and spend a few minutes
wonderin
On Sat, 6 Dec 2014 14:55:33 +0100
, Pavel Machek
wrote:
> Hi!
>
> > > I am accustomed to doing 'echo -n' for most of sysfs anyway. Once in a
> > > while I am a bonehead and forget the '-n' and spend a few minutes
> > > wondering why this thing that worked last week suddenly rejects all
> > > co
On Sat 2014-12-06 13:00:17, Grant Likely wrote:
> On Fri, Oct 24, 2014 at 11:52 AM, Pavel Machek wrote:
> > Hi!
> >
> >> * /sys/class/fpga_manager//firmware
> >> Name of FPGA image file to load using firmware class.
> >> $ echo image.rbf > /sys/class/fpga_manager//firmware
> >
> > I .. still d
Hi!
> > I am accustomed to doing 'echo -n' for most of sysfs anyway. Once in a
> > while I am a bonehead and forget the '-n' and spend a few minutes
> > wondering why this thing that worked last week suddenly rejects all
> > commands. I'm just trying to make my user interface a bit user-friendly
On Fri, Oct 24, 2014 at 3:54 PM, atull wrote:
> On Fri, 24 Oct 2014, Pantelis Antoniou wrote:
>
>> Hi Pavel,
>>
>> > On Oct 24, 2014, at 1:52 PM, Pavel Machek wrote:
>> >
>> > Hi!
>> >
>> >> * /sys/class/fpga_manager//firmware
>> >> Name of FPGA image file to load using firmware class.
>> >> $
On Fri, Oct 24, 2014 at 11:52 AM, Pavel Machek wrote:
> Hi!
>
>> * /sys/class/fpga_manager//firmware
>> Name of FPGA image file to load using firmware class.
>> $ echo image.rbf > /sys/class/fpga_manager//firmware
>
> I .. still don't think this is good idea. What about namespaces?
> The path
> > +int fpga_mgr_write(struct fpga_manager *mgr, const char *buf, size_t count)
> > +{
> > + int ret;
> > +
> > + if (test_and_set_bit_lock(FPGA_MGR_BUSY, &mgr->flags))
> > + return -EBUSY;
> > +
> > + dev_info(mgr->dev, "writing buffer to %s\n", mgr->name);
> > +
> > + ret = __
On Fri, 24 Oct 2014, Pantelis Antoniou wrote:
> Hi Pavel,
>
> > On Oct 24, 2014, at 1:52 PM, Pavel Machek wrote:
> >
> > Hi!
> >
> >> * /sys/class/fpga_manager//firmware
> >> Name of FPGA image file to load using firmware class.
> >> $ echo image.rbf > /sys/class/fpga_manager//firmware
> >
Hi Pavel,
> On Oct 24, 2014, at 1:52 PM, Pavel Machek wrote:
>
> Hi!
>
>> * /sys/class/fpga_manager//firmware
>> Name of FPGA image file to load using firmware class.
>> $ echo image.rbf > /sys/class/fpga_manager//firmware
>
> I .. still don't think this is good idea. What about namespaces?
Hi!
> * /sys/class/fpga_manager//firmware
> Name of FPGA image file to load using firmware class.
> $ echo image.rbf > /sys/class/fpga_manager//firmware
I .. still don't think this is good idea. What about namespaces?
The path corresponds to path in which namespace?
> +int fpga_mgr_write(str
From: Alan Tull
Supports standard ops for low level FPGA drivers.
Various manufacturors' FPGAs can be supported by adding low
level drivers. Each driver needs to register its ops
using fpga_mgr_register().
Exports methods of doing operations to program FPGAs. These
should be sufficient for ind
22 matches
Mail list logo
