New OpenOCD developer here...
I've been doing some work to try to add support for PowerPC. I have an
eval board that uses OSBDM and has a Freescale MPC5634.
It is talking and I can get some things working, but there are many
things not yet handled and some weirdnesses. Experienced devs will
hopef
On 04.05.2015 16:19, De Cesaris, Ivan wrote:
> Hi All,
> jumping on the topic of "the future of OpenOCD", one thing I'd like the core
> group to consider is the license.
>
> Maybe this is not obvious to everyone but the code, being GPL, precludes some
> usages.
> I'm not a lawyer but I can't rele
ivan>> jumping on the topic of "the future of OpenOCD", one thing I'd like the
core group to consider is the license.
This actually "on topic" if you ask me. There is also the subject of a
"contributors agreement" Our legal department asked me if one existed - along
with hundred other questions
Hey Ivan,
Nice to see you back :)
On Mon, May 04, 2015 at 02:19:23PM +, De Cesaris, Ivan wrote:
> Maybe this is not obvious to everyone but the code, being GPL,
> precludes some usages. I'm not a lawyer but I can't release
> internal developed code for new silicon to any external customer
>
"De Cesaris, Ivan" wrote:
>
>Hi All,
>jumping on the topic of "the future of OpenOCD", one thing I'd like the core
>group to consider is the license.
>
>Maybe this is not obvious to everyone but the code, being GPL, precludes some
>usages.
>I'm not a lawyer but I can't release internal developed
Hi All,
jumping on the topic of "the future of OpenOCD", one thing I'd like the core
group to consider is the license.
Maybe this is not obvious to everyone but the code, being GPL, precludes some
usages.
I'm not a lawyer but I can't release internal developed code for new silicon to
any extern
