I am currently working on a driver for a PCI card. To access this card I have
writen a small uio kernel driver for Linux based on the concept from mrfio2.
In the asynDriver that I'm working on I use devlib2 to get access to the
mapped memory regions of the card following the concept of evrMrmApp from
mrfio2. In mrfCommon a lot of macros (BITSET, BITCLR, READS and WRITE for
various bitwidth) are defined.
Should these macros not be part of devlib2? This way other modules could
profit from this work much easier. Pulling these files into my project would
require to install the mrfio2 module even if I do not have the hardware. Not
thinking about license conflicts that might arise if I copy the code over to
my project.
Regards,
Jörn Dreyer
--
Dr. Joern Dreyer
HIBEF DAQ + Controls
Institut für Strahlenphysik
Helmholtz-Zentrum Dresden - Rossendorf e.V
Helmholtz-Zentrum Dresden - Rossendorf e.V (HZDR)
Bautzner Landstraße 400, 01328 Dresden
Vorstand: Prof. Dr. Dr. h. c. Roland Sauerbrey, Dr. Ulrich Breuer
Vereinsregister: VR 1693 beim Amtsgericht Dresden
- Replies:
- Re: Question regarding the usage of devlib2 Michael Davidsaver
- Navigate by Date:
- Prev:
RE: Request: Survey of EPICS PVA ( a.k.a EPICS V4) users [email protected]
- Next:
Re: Request: Survey of EPICS PVA ( a.k.a EPICS V4) users Shen, Guobao
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Bayer to RGB areaDetector [email protected]
- Next:
Re: Question regarding the usage of devlib2 Michael Davidsaver
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|