Software Driver for Qsys Subsystem

Thanks for the reply!

Where would I put that .h file? In the case of a component driver, I would store it with the driver (in subversion), and create a _sw.tcl script so that it gets incorporated into the BSP. If I have a library component (or in this case, a qsys subsystem) in version control somewhere, I would like to store the software files with it, so that I can just check it out once. I could store the driver with my software code, or in a separate SVN path which I can check out as an external along with my software code; and I may have to accept that. But I think it would be preferable if it could be stored along with the qsys subsystem, and automatically included in the code by the SBT when that component is instantiated in the system.

In fact, generally I'm thinking of a driver with a lot more functionality than just macros for register access, but I think the issue applies both ways.