On Thu, Apr 16, 2009 at 9:55 AM, Xiaofan Chen <[email protected]> wrote: > I think I understand what Xiaochen says. The issue has nothing > to do with ARM946ES or the existing OpenOCD code. > The issue is that ARM946E is not supported and he used > ARM966E with an ARM946E chip and he found out this is the > real problem in his second email. So now he is asking whether > Openocd has plan to support arm946es in the future.
I haven't read up on the differences, but they appear to be slight. Perhaps the code is all there and it is "just" a matter of making a new driver entry file? In opensource there are not much in the way of "plans" in the normal sense in a commercial company. Either someone publishes a viable patch or they do not. Your have three choices: - contribute to a patch yourself. Either the whole or part. Your posting in clarifying the problem is a first step in this direction. - pay somebody to write the patch for you - hope that somebody will publish a patch -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
