On 06/07/15 18:24, Dmitry Kalinkin wrote:
Some functionality was dropped as it was not good practice
(such as receiving VME interrupts in user space, it's not really doable if
the slave card is Release On Register Access rather than Release on
Acknowledge),
Didn't know about RORA. I wonder
On 07/07/15 08:08, Alessio Igor Bogani wrote:
I would be glad to try it if the maintainer is willing to receive this
type of changes.
Such requirements have come up in the past. I'd welcome such support
being contributed to the kernel. My view has been that such an API could
be built on top
On 07/07/15 13:51, Alessio Igor Bogani wrote:
Current VME stack links windows not to the boards, but to device drivers.
Driver
could potentially minimise window usage within it’s scope (any sort of
window
reusing, like mapping whole A16 once to be used with all boards), but this
won’t
work
On 07/07/15 11:52, Dmitry Kalinkin wrote:
The API I had in mind would have only vme_master_read and
vme_master_write that would take absolute addresses (not relative to
any window). These variants of access functions would then try to
reuse any window that is already able to serve the request
On 08 Jul 2015, at 16:57, Martyn Welch martyn.we...@ge.com wrote:
On 07/07/15 11:52, Dmitry Kalinkin wrote:
The API I had in mind would have only vme_master_read and
vme_master_write that would take absolute addresses (not relative to
any window). These variants of access functions
On 08 Jul 2015, at 16:41, Martyn Welch martyn.we...@ge.com wrote:
On 07/07/15 13:51, Alessio Igor Bogani wrote:
Current VME stack links windows not to the boards, but to device drivers.
Driver
could potentially minimise window usage within it’s scope (any sort of
window
reusing, like
Hi Dmitry,
On 6 July 2015 at 19:24, Dmitry Kalinkin dmitry.kalin...@gmail.com wrote:
[...]
I'm not a VME expert, but it seems that VME windows are a quiet limited
resource
no matter how you allocate your resources. Theoretically we could put up to 32
different boards in a single crate, so
Hi Dmitry,
On 7 July 2015 at 12:47, Dmitry Kalinkin dmitry.kalin...@gmail.com wrote:
[...]
The API I had in mind would have only vme_master_read and vme_master_write
that would take absolute addresses (not relative to any window). These
variants
of access functions would then try to reuse any
Hi Alessio,
[Sorry for double post]
On 07 Jul 2015, at 10:08, Alessio Igor Bogani alessioigorbog...@gmail.com
wrote:
Hi Dmitry,
On 6 July 2015 at 19:24, Dmitry Kalinkin dmitry.kalin...@gmail.com wrote:
[...]
I'm not a VME expert, but it seems that VME windows are a quiet limited
On 07 Jul 2015, at 15:51, Alessio Igor Bogani alessioigorbog...@gmail.com
wrote:
snip
Current VME stack links windows not to the boards, but to device drivers.
Driver
could potentially minimise window usage within it’s scope (any sort of
window
reusing, like mapping whole A16 once to be
On Mon, Jul 6, 2015 at 4:22 PM, Martyn Welch martyn.we...@ge.com wrote:
Sorry about the *really* late reply, loads of emails some how missed my
periodic search of the mailing list.
I'm happy with the addition of DMA, just not sure whether it's worth adding
an extra device file just to handle
On Mon, Jul 6, 2015 at 5:48 PM, Martyn Welch martyn.we...@ge.com wrote:
On 06/07/15 14:50, Dmitry Kalinkin wrote:
On Mon, Jul 6, 2015 at 4:22 PM, Martyn Welch martyn.we...@ge.com wrote:
Sorry about the *really* late reply, loads of emails some how missed my
periodic search of the mailing
On 13/06/15 01:28, Greg Kroah-Hartman wrote:
On Thu, May 28, 2015 at 03:07:05PM +0300, Dmitry Kalinkin wrote:
This introduces a new dma device that provides a single ioctl call that
provides DMA read and write functionality to the user space.
Signed-off-by: Dmitry Kalinkin
On 06/07/15 14:50, Dmitry Kalinkin wrote:
On Mon, Jul 6, 2015 at 4:22 PM, Martyn Welch martyn.we...@ge.com wrote:
Sorry about the *really* late reply, loads of emails some how missed my
periodic search of the mailing list.
I'm happy with the addition of DMA, just not sure whether it's worth
On Thu, May 28, 2015 at 03:07:05PM +0300, Dmitry Kalinkin wrote:
This introduces a new dma device that provides a single ioctl call that
provides DMA read and write functionality to the user space.
Signed-off-by: Dmitry Kalinkin dmitry.kalin...@gmail.com
Cc: Igor Alekseev
This introduces a new dma device that provides a single ioctl call that
provides DMA read and write functionality to the user space.
Signed-off-by: Dmitry Kalinkin dmitry.kalin...@gmail.com
Cc: Igor Alekseev igor.aleks...@itep.ru
---
drivers/staging/vme/devices/vme_user.c | 201
16 matches
Mail list logo
