> On 13 Jul 2018, at 04:27, Alan Carvalho de Assis <[email protected]> wrote:
>
> Hi Tim,
>
> Basically some openocd user needs to test it and give a +1 and then an
> OpenOCD developer need to verify the code quality and also give +1 or
> propose some modification to your patch.
Given that Tim is the head of the RISC-V debug committee and also the
maintainer of the RISC-V OpenOCD, I think we should be more flexible.
His code will definitely evolve as the RISC-V specs will evolve, so I would not
be very concerned with the functionality of the current code, since I'm
convinced Tim's tests were more thorough than anyone else can do.
Being a new target, I suggest to check mainly if the additions have any
negative impact on the existing targets; in my opinion there are no such
problems, and I recommend to accept the patch.
Regards,
Liviu
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel