Experimental Physics and
Industrial Control System

I understand Ralph's reasoning very well.

However, If we follow the reasoning that "Stuff that deals with hardware buses is not essential”,
then the question also arises why we support VxWorks and RTEMS.
We do this only to support special hardware (in these cases mostly VMEbus and PMC/PCI bus)?

I would of course be sad if the support for it would be omitted ;-)

I would be very happy if we could replace devLib with devLib2.

Without the support of devLib it is very difficult to use the bus systems like PCI/PMC/VMEbus etc. in a general way
and independent of the host/target system.

Those were my 2ct.

Heinz


> On 12. Oct 2018, at 09:04, Ralph Lange <[email protected]> wrote:
>
> Ok, got it.
>
> So, to add my 2cts, I would be all for devLib and devLib2 being combined (or whatever is necessary), and both moved out of Base.
>
> Stuff that deals with hardware buses is not essential.
> Maintenance and testing need specific hardware, tests can not be run on our common CI infrastructure using virtual machines or containers.
> Most if not all software modules that use these libraries are not in Base.
> IMHO, there were (and still are) a number of reasons to unbundle hardware specific EPICS modules.
>
> Cheers,
> ~Ralph
>
>
>
> On Thu, 11 Oct 2018 at 17:39, Heinz Junkes <[email protected]> wrote:
> Hi Ralph,
> Timo has already written it.
>
> devLib2 extends devLib "only" by the PCI access,  not fixed on a specific card but in general (VMEbus + PCIbus)
>
> Heinz
>
> > On 11. Oct 2018, at 15:17, Ralph Lange <[email protected]> wrote:
> >
> > Hi Heinz,
> >
> > Generally, EPICS Base does not contain utilities or support for specific hardware.
> >
> > Cheers,
> > ~Ralph
> >
> >
> > On Thu, 11 Oct 2018 at 13:47, Heinz Junkes <[email protected]> wrote:
> > Hello guys,
> >
> > what is the reason why devLib2 is not a component of epics-base?
> > Not yet sufficiently tested?
> >
> > Heinz
> >
> > ----------------------------------------------------------------------
> > Das FHI verarbeitet, speichert und loescht Daten im Rahmen seiner
> > Geschaeftstaetigkeit gemaess der Datenschutz-Grundverordnung (DSGVO)
> > [General Data Protection Regulation (GDPR)] der Europaeischen Union.
> >
>
>
> ----------------------------------------------------------------------
> Das FHI verarbeitet, speichert und loescht Daten im Rahmen seiner
> Geschaeftstaetigkeit gemaess der Datenschutz-Grundverordnung (DSGVO)
> [General Data Protection Regulation (GDPR)] der Europaeischen Union.
>


----------------------------------------------------------------------
Das FHI verarbeitet, speichert und loescht Daten im Rahmen seiner
Geschaeftstaetigkeit gemaess der Datenschutz-Grundverordnung (DSGVO)
[General Data Protection Regulation (GDPR)] der Europaeischen Union.