The I2C asyn driver could be considered for going into asyn itself, since it is conceptually similar to the serial, IP, GPIB, USBTMC, and VXI11 drivers.
Note that "ip" is really not for software related to Industry Pack modules any more. Most industry pack drivers now have their own modules (ip330, ipUnidig, dac128V, softGlue, ipac for ipOctal). "ip" is really now software for asynOctet devices (serial, GPIB, TCP) that do not have another home like "vac" and "delayGen". "ip" is no longer a good name for it.
Similarly "std" was originally the home for a lot "standard" beamline control stuff. Most of this has now been moved to other modules (calc, busy, optics, sscan), so "std" is more like "misc" now.
Mark
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Pete Jemian
Sent: Wednesday, November 25, 2015 11:10 AM
To: [email protected]
Subject: Re: Device Support for I2C and GPIO
Michael describes a good procedure for completely new functionality.
New modules should provide support distinct from other modules.
This _might_ have a place in one of the existing synApps modules. This
is not "ip" functionality (related to Industry Pack modules), not
"calc", not "optics", perhaps "std" is the catchall module for new
synApps support?
On 11/25/2015 9:08 AM, Michael Davidsaver wrote:
On 11/25/2015 03:08 AM, Florian Feldbauer wrote:
I would like to upload the sources to github. Is it possible to upload
it to the "epics-modules" group?
At this point there isn't any established criteria for when/if
repositories in this group are created.
It would suggest starting with a repository under your own account (what
I do), then think about moving to epics-modules at some later date,
which isn't difficult.
That said, if you want to go straight to epics-modules I'm inclined to
just add it. Let me know if you want to do this and I'll do this in a
day or so, assuming no one objects. Of course, first you need to solve
the hard problem, the repository name ;)
Michael