On Wednesday, November 10, 2010 11:55:19 Jonathan Stroud wrote: > What is the current philosophy on the "data" directory in UrJtag. Are > users still encouraged to add their parts here and hopefully contribute > them upstream, or are users being encouraged to just dump all of their > BSDL files to a directory and include them instead? > > I kinda like the idea of being able to just use BSDL files, however I have > been converting them and sticking them in the data directory because stuff > like "print chain" just looks prettier this way because it fills in all of > the other details.
i think it depends. in general, i think people are being encouraged to use BSDL files since these are likely to be more "up-to-date". certainly with "dynamic" parts like FPGAs where the pin list has no real meaning, BSDLs are encouraged. but when dealing with released SoC's, entries in data/ probably make sense. certainly for the parts i support, i keep entries in there so users dont have to fetch the BSDLs themselves. > I also like converting them ahead of time so I can fix > up the BSDL files when I run into incompatibilities with the bsdl parser. if there are bugs in the BSDL parser, feel free to submit fixes -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
