On Tuesday, August 24, 2010 05:08:49 Frans Meulenbroeks wrote: > 2010/8/23 Frans Meulenbroeks: > > Also is it guaranteed/defined that the tdi and tms argumetns to clock > > are 0 or 1? Or can there also be other values. > > If they are guaranteed 0 or 1 we can eliminate the followigng lines > > from the gpio.c gpio_clock function > > tms = tms ? 1 : 0; > > tdi = tdi ? 1 : 0; > > This question still remains open.
i dont think any other value makes sense. we're talking about lines here that can either be high or low. no value other than 0 or 1 is valid for any jtag line that i can see. imo, cable drivers shouldnt have to worry about normalizing the values to 1 or 0. not that higher layers should be sending this down, but if they did, we can start a new discussion on the topic as to where is the best place to use "!!" to normalize the actual value. so if you wanted to send a patch to change a cable driver to assume values of 1 or 0, then that's OK by me. -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
