> On 18 Sep 2015, at 05:46, Martyn Welch wrote:
>
>
>
> On 18/09/15 00:01, dmitry.kalin...@gmail.com wrote:
>> From: Dmitry Kalinkin
>>
>> The current VME bus error handler adds errors to the bridge error list.
>> vme_master_{read,write} then traverses that list to look for relevant
>> error
On Fri, Sep 18, 2015 at 5:46 AM, Martyn Welch wrote:
>
>
> On 18/09/15 00:01, dmitry.kalin...@gmail.com wrote:
>>
>> From: Dmitry Kalinkin
>>
>> The current VME bus error handler adds errors to the bridge error list.
>> vme_master_{read,write} then traverses that list to look for relevant
>> erro
On 18/09/15 00:01, dmitry.kalin...@gmail.com wrote:
From: Dmitry Kalinkin
The current VME bus error handler adds errors to the bridge error list.
vme_master_{read,write} then traverses that list to look for relevant
errors.
Such scheme didn't work well for accesses going through vme_master_m
From: Dmitry Kalinkin
The current VME bus error handler adds errors to the bridge error list.
vme_master_{read,write} then traverses that list to look for relevant
errors.
Such scheme didn't work well for accesses going through vme_master_mmap
because they would also allocate a vme_bus_error, bu
