Hi Steven,

Am 20.11.18 um 16:14 schrieb Steven Stallion:
> Hi Oleksij,
> 
> On Tue, Nov 20, 2018 at 6:41 AM, Oleksij Rempel <li...@rempel-privat.de
> <mailto:li...@rempel-privat.de>> wrote:
> 
>     Hi all,
> 
>     i started this discussion on the irc #openocd. As PaulFertser suggested,
>     lets move it to the mailing list.
> 
>     To make at least some of the commands more consistent, i decided to
>     rework adapter related part. Initial patch is here:
>     http://openocd.zylin.com/4774
> 
>     Here are the old variants of adapter related commands:
>     ftdi_location <location>
>     interface <name>
>     interface_list
>     interface_name
>     adapter_nsrst_delay
>     adapter_nsrst_assert_width
>     interface_transports
>     adapter_khz
> 
>     here is my new:
>     adapter usb location <location> (set usb location of usb adapter)
>     adapter driver set <name> (select adapter driver)
>     adapter driver get (get configured driver name)
>     adapter driver list (list build in drivers)
>     adapter srst delay_after (delay after srst deasserted)
>     adapter srst width (assertion pulse width)
>     adapter transports (set list of supported transports by adapter)
>     adapter khz (set clock rate of TCLK line)
> 
>     By "adapter khz" and "adapter transports", i'm not 100% sure. For the
>     firs one, I can imagine some thing like "adapter tclk rate <rate>".
> 
>     Comments, suggestions, ideas related to this topic are welcome!
> 
> 
> Apart from the mechanical aspects of having a shared command context
> across multiple modules, this is a rather radical departure from how
> targets are configured today and could have wide-ranging consequences.

For example?

> Out of curiosity, what is driving you toward this conclusion? Is there a
> technical issue that you're trying to solve with this proposal?

The technical issue is only behind the "adapter usb location" command.
Problematic integration in to labgrid:
https://labgrid.readthedocs.io/en/latest/

Other part of proposal was inspired with mental disorder, in which I
run, by work on the src/jtag/adapter.c
You will probably notice this by reading OpenOCD documentation - the
words "adapter" and "interface" are usually mixed and used as synonyms
for same command group.
I understand that it is historically grown. So why not clean it up?

-- 
Regards,
Oleksij


_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to