> >>>> Worse. My ppmc driver exports pins based on what devices it > >>>> detects on the parallel port bus. (I think the Mesa drivers > >>>> do something similar.) > >>> How do you write configuration for these changing ports today? > >>> ... > >>> > >> By hand, based on sample configs. ... > >> The PPMC instantiates encoder, DAC and DIO functions based > >> on the number of boards plugged into the PPMC motherboard. > >> ... your Hal files need to be match that. > > Back annotation from detected devices would be useful to get the correct > > symbols into gschem. There dynamically generated Hal so the Hal must match. > > If connections are drawn visually in gschem and exported to Hal it will be > > the same. > > > > I would say get gschem to Hal would be very useful although user must know > > which symbols to add. > > > > Are there a method to probe the hardware without a *.hal file? > > > > > Well, I have a diagnostic program that gives the info, not > sure if that is any help.
I could see information about the device is sent during startup. To probe the device driver need to be loaded without any connections in the *.hal file, could this be done? ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
