[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170809143128.GI30723@lunn.ch>
Date: Wed, 9 Aug 2017 16:31:28 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Oleksandr Shamray <oleksandrs@...lanox.com>
Cc: gregkh@...uxfoundation.org, arnd@...db.de,
devicetree@...r.kernel.org, jiri@...nulli.us,
system-sw-low-level@...lanox.com, openbmc@...ts.ozlabs.org,
linux-kernel@...r.kernel.org,
openocd-devel-owner@...ts.sourceforge.net, mec@...ut.net,
robh+dt@...nel.org, joel@....id.au, linux-serial@...r.kernel.org,
vadimp@...llanox.com, tklauser@...tanz.ch,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [patch v2 0/2]
On Mon, Aug 07, 2017 at 05:17:45PM +0300, Oleksandr Shamray wrote:
> When a need raise up to use JTAG interface for system's devices
> programming or CPU debugging, it could be done from the external
> JTAG master controller.
>
> For such purpose, usually the user layer
> application implements jtag protocol or using a proprietary
> connection to vendor hardware.
> This method is slow and not generic.
>
> We propose to implement general JTAG interface and infrastructure
> to communicate with user layer application.
Hi Oleksandr
You might find this discussion interesting:
https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2017-August/004721.html
You are defining a new ABI here, so linux-abi should be involved in
the discussion of these patches.
Andrew
Powered by blists - more mailing lists