On Wed, 2009-05-20 at 22:59 -0700, Zach Welch wrote:
> On Wed, 2009-05-20 at 22:54 -0700, Rick Altherr wrote:
> > On May 20, 2009, at 10:31 PM, Zach Welch wrote:
> > 
> > > On Wed, 2009-05-20 at 22:23 -0700, Rick Altherr wrote:
> > >> On Mar 25, 2009, at 2:54 PM, joern kaipf wrote:
> > >>
> > >>> * autodetection if FS or HS device attachted -> adapt tck max
> > >>> * enable adaptive clocking if HS device attached and jtag_khz = 0 in
> > >>> cfg (not
> > >>> tested yet)
> > >>>
> > >>> Note:
> > >>> The HS devices are currently only support by the drivers from FTDI
> > >>> and not
> > >>> from the libftdi. So using libftdi and RTCK support will cause a  
> > >>> error
> > >>> message.
> > >>> <ft2232.patch>_______________________________________________
> > >>> Openocd-development mailing list
> > >>> Openocd-development@lists.berlios.de
> > >>> https://lists.berlios.de/mailman/listinfo/openocd-development
> > >>
> > >>
> > >> This doesn't appear to have been applied, but doesn't apply cleanly  
> > >> to
> > >> HEAD.  Is there an updated version available?
> > >
> > > I cleaned it up and posted it here:
> > >
> > >   
> > > https://lists.berlios.de/pipermail/openocd-development/2009-April/005479.html
> > >
> > > It probably needs a little more work.
> > >
> > > Cheers,
> > >
> > > Zach
> > >
> > >
> > 
> > 
> > It looks like even _that_ version doesn't apply cleanly since the last  
> > batch of updates to the ft2232 driver.
> 
> Bummer, but that is where I would start development.  I recommend
> applying it to the old revision ('svn up -r${PATCH_REV}') then letting
> SVN help with the merge through an 'svn up'.  You are probably more
> familiar with the code and can figure out what to do better than I.

Whoops... looks like this patch almost slipped through the cracks.
I will take a stab at it shortly and repost it, unless you started it.

--Z
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to