diff options
| author | David Brownell <dbrownell@users.sourceforge.net> | 2009-11-09 13:16:32 -0800 |
|---|---|---|
| committer | David Brownell <dbrownell@users.sourceforge.net> | 2009-11-09 13:16:32 -0800 |
| commit | d70d9634bf6ab73ec4f2ac1e77012785770b460a (patch) | |
| tree | e2cfbb23ab2a145dbd465832415de867904c247f /testing/examples/LPC2148Test/test_ram.hex | |
| parent | 9253ce9baea6f7b5ef3fc53b4bc0cfbff48194f4 (diff) | |
| download | openocd+libswd-d70d9634bf6ab73ec4f2ac1e77012785770b460a.tar.gz openocd+libswd-d70d9634bf6ab73ec4f2ac1e77012785770b460a.tar.bz2 openocd+libswd-d70d9634bf6ab73ec4f2ac1e77012785770b460a.tar.xz openocd+libswd-d70d9634bf6ab73ec4f2ac1e77012785770b460a.zip | |
finish removing deprecated/obsolete commands
It's been about a year since these were deprecated and, in most
cases, removed. There's no point in carrying that documentation,
or backwards compatibility for "jtag_device" and "jtag_speed",
around forever. (Or a few remnants of obsolete code...)
Removed a few obsolete uses of "jtag_speed":
- The Calao stuff hasn't worked since July 2008. (Those Atmel
targets need to work with a 32KHz core clock after reset until
board-specific init-reset code sets up the PLL and enables a
faster JTAg clock.)
- Parport speed controls don't actually work (tops out at about
1 MHz on typical HW).
- In general, speed controls need to live in board.cfg files (or
sometimes target.cfg files), not interface.cfg ...
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'testing/examples/LPC2148Test/test_ram.hex')
0 files changed, 0 insertions, 0 deletions