On Fri, Mar 5, 2021 at 12:00 PM Ooi, Cinly <[email protected]> wrote:
> Hi All > > > > I had written a driver which uses the minidriver interface, It is working > fine and we plan to open source it in a few weeks (>5) time when all > internal due-diligence are done. > > > > Before I started I already noted that only zy1000.c is using the > minidriver interface, and it itself is scheduled for removal. With that > only use case gone it will mean there is a high chance that interface will > be removed. This meant that I have to come here and ask the OpenOCD > development team whether do they have plans to deprecate and remove this > interface? and if so, when? And is there a replacement? > > > Hi! In fact I have had long standing plans (5+ years) to get rid of this interface, with ZY1000 being the only blocker. The goal at the time was to be able to improve the adapter API without being dragged down by how the minidriver layer was implemented. Nowadays, the minidriver API still stands, I don't have much time to spend on OpenOCD so I probably won't do any of this myself. The minidriver interface was mainly to support exactly the ZY1000 type of "intelligent" adapters which run openocd on the "adapter" itself. A side effect is that when building with a minidriver, ALL other drivers will be unavailable in that build. If the adapter you are adding support for is not of this type (or possibly even if it is) I strongly suggest you transition to the regular adapter interface which all other adapters use. This might not necessarily be that difficult, depending on what you have done so far. It would be interesting to know why the minidriver approach was chosen. What kind of adapter are we talking about? /Andreas
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
