Hello Hans
Am Donnerstag, den 19.07.2012, 01:47 +0200 schrieb Hans J. Koch:
> You'll hear from me soon, thanks for your work! Comments and reviews
> from others are welcome...
Is there any progress on this topic?
--
Gruß
Dominic
Frankfurt Institute for Advanced Studies (FIAS)
Hello Hans
Am Donnerstag, den 19.07.2012, 01:47 +0200 schrieb Hans J. Koch:
You'll hear from me soon, thanks for your work! Comments and reviews
from others are welcome...
Is there any progress on this topic?
--
Gruß
Dominic
Frankfurt Institute for Advanced Studies (FIAS)
Am Montag, den 16.07.2012, 23:58 +0200 schrieb Hans J. Koch:
> Try to hack up a patch to add generic BAR mapping to uio_pci_generic.c
> and post it for review.
>
Here we go ...
>
Signed-off-by: Dominic Eschweiler
diff --git a/drivers/uio/uio_pci_generic.c
b/drivers/uio/uio_pci_gen
Am Montag, den 16.07.2012, 23:58 +0200 schrieb Hans J. Koch:
Try to hack up a patch to add generic BAR mapping to uio_pci_generic.c
and post it for review.
Here we go ...
Signed-off-by: Dominic Eschweiler eschwei...@fias.uni-frankfurt.de
diff --git a/drivers/uio/uio_pci_generic.c
b/drivers
Am Freitag, den 13.07.2012, 21:19 +0300 schrieb Michael S. Tsirkin:
>
> UIO has the same property, doesn't it? Multiple users can
> access device memory through sysfs.
Indeed, that's a similar problem. I haven't tried it (yet), but this
particular problem can maybe circumvented by using mmap
Am Freitag, den 13.07.2012, 21:19 +0300 schrieb Michael S. Tsirkin:
UIO has the same property, doesn't it? Multiple users can
access device memory through sysfs.
Indeed, that's a similar problem. I haven't tried it (yet), but this
particular problem can maybe circumvented by using mmap with
Am Freitag, den 13.07.2012, 16:18 +0200 schrieb Hans J. Koch:
> If somebody maps the card's memory through the UIO driver and somebody
> else also maps it using sysfs, that is possible. What happens if both
> write to the same hardware registers is a different topic. Writing a
> driver implies
Am Freitag, den 13.07.2012, 16:22 +0300 schrieb Michael S. Tsirkin:
> Could you give an example of the problem? How do you bind
> both UIO and another driver to the same device?
Sorry, I'm looking on it from the user-space perspective. Maybe I'm
wrong, but I can give you an example :
lspci -v
Am Freitag, den 13.07.2012, 02:16 +0300 schrieb Michael S. Tsirkin:
> My concern was people will ask for more and more stuff that pci
> sysfs already has.
> If we do add these is there a way to not duplicate code from pci?
I have some concerns about the placing for the BAR mapping code inside
Am Freitag, den 13.07.2012, 02:16 +0300 schrieb Michael S. Tsirkin:
My concern was people will ask for more and more stuff that pci
sysfs already has.
If we do add these is there a way to not duplicate code from pci?
I have some concerns about the placing for the BAR mapping code inside
the
Am Freitag, den 13.07.2012, 16:22 +0300 schrieb Michael S. Tsirkin:
Could you give an example of the problem? How do you bind
both UIO and another driver to the same device?
Sorry, I'm looking on it from the user-space perspective. Maybe I'm
wrong, but I can give you an example :
lspci -v
...
Am Freitag, den 13.07.2012, 16:18 +0200 schrieb Hans J. Koch:
If somebody maps the card's memory through the UIO driver and somebody
else also maps it using sysfs, that is possible. What happens if both
write to the same hardware registers is a different topic. Writing a
driver implies some
12 matches
Mail list logo