On Fri, May 5, 2017 at 3:59 PM, Moritz Fischer wrote:
> On Thu, Apr 20, 2017 at 7:09 AM, Alan Tull wrote:
>> During a device tree overlay pre-apply notification, the check
>> for child FPGA regions can happen slightly earlier. This saves
>> us from allocating
On Fri, May 5, 2017 at 3:59 PM, Moritz Fischer wrote:
> On Thu, Apr 20, 2017 at 7:09 AM, Alan Tull wrote:
>> During a device tree overlay pre-apply notification, the check
>> for child FPGA regions can happen slightly earlier. This saves
>> us from allocating the FPGA image info that just gets
On Thu, Apr 20, 2017 at 7:09 AM, Alan Tull wrote:
> During a device tree overlay pre-apply notification, the check
> for child FPGA regions can happen slightly earlier. This saves
> us from allocating the FPGA image info that just gets thrown
> away.
>
> This is a baby step in
On Thu, Apr 20, 2017 at 7:09 AM, Alan Tull wrote:
> During a device tree overlay pre-apply notification, the check
> for child FPGA regions can happen slightly earlier. This saves
> us from allocating the FPGA image info that just gets thrown
> away.
>
> This is a baby step in refactoring the
During a device tree overlay pre-apply notification, the check
for child FPGA regions can happen slightly earlier. This saves
us from allocating the FPGA image info that just gets thrown
away.
This is a baby step in refactoring the FPGA region code to
separate out common FPGA region code from
During a device tree overlay pre-apply notification, the check
for child FPGA regions can happen slightly earlier. This saves
us from allocating the FPGA image info that just gets thrown
away.
This is a baby step in refactoring the FPGA region code to
separate out common FPGA region code from
6 matches
Mail list logo