)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000687,"name":"Tomas Vanek","display_name":"Tomas Vanek","email":"vanekt@fbl.cz","username":"vanekt"},"change_message_id":"eafb392c55c8fd6e661c7a1111acb2a8eccc29bc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1ccdff67_f83a386e","updated":"2025-02-12 10:58:12.000000000","message":"Nice! Thanks","commit_id":"ae5674aa8f93cbeb76b383723b8160f771837896"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"0b11de6214fb46ed3bb4d3b42527db506d487b69","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b404e99d_58f349ff","updated":"2025-02-12 12:26:41.000000000","message":"Nice, thanks!\n\nTwo things from my side. First, please document the new command behaviour and mention that the listed transports are the supported transports of the *driver* and not necessarily of the adapter. The driver may support more transports than an attached probe. Second, do we want to make the supported transports of an adapter discoverable? In the future this might be nice to have and when we rework the transport framework we should at least think about it.","commit_id":"ae5674aa8f93cbeb76b383723b8160f771837896"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"2cef39922c4717d37819de4d7033aeb5562337e5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6655eeb9_30189cb2","in_reply_to":"08ab6472_e4179008","updated":"2025-03-15 10:32:48.000000000","message":"That\u0027s out of the scope of this patch.\n\nI have in mind something like this, but not specific for one type.\n`adapter detect` or `adapter autodetect`\nthat also try to lists adapters that have incorrect USB access permission.\nClearly, restricting it with an optional `adapter driver jlink` is a good idea.\n\nMaybe we would need an API `.autodetect` in `struct adapter_driver` and sometimes also a dedicated `tcl/interface/\u003cadapter_name\u003e-autodetect.cfg` for example to list all the possible USB IDs (think at all the FTDI flavors available ...).\n\nI expect some adapter could not be possible to be autodetected.\nE.g. GPIO bitbanging; in such case, reporting that there are GPIO available could be enough.","commit_id":"ae5674aa8f93cbeb76b383723b8160f771837896"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"aad02443341290026a314e6924141cfd0580e9c1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"08ab6472_e4179008","in_reply_to":"20ad74da_82134617","updated":"2025-02-16 10:33:00.000000000","message":"Yes, sounds good. However, I would prefer if there is also a way to autodetect only driver-specific devices. Maybe something like:\n\n```adapter driver jlink\nadapter autodetect```\n\nTo detect all attached probes, we could iterate over all available drivers? The idea is to have a small set of basic functionality in C and the rest in Tcl.","commit_id":"ae5674aa8f93cbeb76b383723b8160f771837896"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"dbbfda58636b932603d9690a3aec0b5329f2f90e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"dd68e01c_5d15c0aa","in_reply_to":"6655eeb9_30189cb2","updated":"2025-03-16 13:34:01.000000000","message":"\u003e That\u0027s out of the scope of this patch.\n\nYes, absolutely! I just wanted to exchange a few thoughts on this topic.","commit_id":"ae5674aa8f93cbeb76b383723b8160f771837896"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"025fbbc14ea459c2900b7a402c1f8feb20c5d8b5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"20ad74da_82134617","in_reply_to":"b404e99d_58f349ff","updated":"2025-02-12 16:46:34.000000000","message":"Yep, missing doc. Will send a v2.\nThis command `adapter list` gives the list of available drivers, not really the list of connected adapters and their supported transport.\n\nI think we could add in `struct adapter_driver` an optional method `.autodetect` that try to find and list every present adapter supported by the driver. Eventually using a special file in `tcl/interface/` (e.g. listing all possible USB IDs).\nThen a new command `adapter autodetect` could be used to list all adapters for all the drivers, including info for selecting the specific one (e.g. USB serial and USB location).\nThis could be used for:\n`openocd -c \"adapter autodetect; shutdown\"`","commit_id":"ae5674aa8f93cbeb76b383723b8160f771837896"}],"doc/openocd.texi":[{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"de3dcc2e14150e64824f06e474dfd78454ed3f5c","unresolved":true,"context_lines":[{"line_number":2415,"context_line":"List the debug adapter drivers that have been built into"},{"line_number":2416,"context_line":"the running copy of OpenOCD."},{"line_number":2417,"context_line":""},{"line_number":2418,"context_line":"The output is formatted as a TCL dictionary indexed by the adapter name"},{"line_number":2419,"context_line":"and containing the transports in a TCL list."},{"line_number":2420,"context_line":"@example"},{"line_number":2421,"context_line":"dummy  @{ jtag @}"}],"source_content_type":"text/x-texinfo","patch_set":2,"id":"65d54fa3_9e3cbf68","line":2418,"updated":"2025-04-20 08:01:59.000000000","message":"TCL -\u003e Tcl.\n\n(if you prefer I can rebase my patch series on this one)","commit_id":"3eb6c25cfed082f7c87bd7e06fb737c99e736526"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"0dd39ff5b721996751ba6c4464152e8c3e761896","unresolved":false,"context_lines":[{"line_number":2415,"context_line":"List the debug adapter drivers that have been built into"},{"line_number":2416,"context_line":"the running copy of OpenOCD."},{"line_number":2417,"context_line":""},{"line_number":2418,"context_line":"The output is formatted as a TCL dictionary indexed by the adapter name"},{"line_number":2419,"context_line":"and containing the transports in a TCL list."},{"line_number":2420,"context_line":"@example"},{"line_number":2421,"context_line":"dummy  @{ jtag @}"}],"source_content_type":"text/x-texinfo","patch_set":2,"id":"31cce1c0_1751ffeb","line":2418,"in_reply_to":"65d54fa3_9e3cbf68","updated":"2025-04-29 07:39:42.000000000","message":"Thanks for the review.\nIt\u0027s a shame I reviewed your series and did not thought to verify mine.\nI modified it with gerrit editor","commit_id":"3eb6c25cfed082f7c87bd7e06fb737c99e736526"}]}