[prev in list] [next in list] [prev in thread] [next in thread]
List: openocd-development
Subject: Re: [OpenOCD-devel] GigaDevice support
From: kristof.mulier () telenet ! be
Date: 2020-11-30 13:01:58
Message-ID: 1532283102.41548744.1606741318839.JavaMail.zimbra () telenet ! be
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Tomas,
> "Please believe me, we (maintainers) have no time to gather changes from every fork \
> of OpenOCD on github and everywhere. And moreover if we did so it would be quite \
> unfair to the authors of lots of changes which are already waiting in the gerrit."
I didn't realize this before. My apologies. I'll contact GigaDevice and explain it to \
them.
About the free GigaDevice boards, are you (and/or some of your co-workers) \
interested?
Kind regards,
Kristof Mulier
Van: "openocd-devel" <openocd-devel@lists.sourceforge.net>
Aan: "openocd-devel" <openocd-devel@lists.sourceforge.net>
Verzonden: Maandag 30 november 2020 10:50:40
Onderwerp: Re: [OpenOCD-devel] GigaDevice support
Hi Kristof,
On 22/11/2020 11:57, [ mailto:kristof.mulier@telenet.be | kristof.mulier@telenet.be ] \
wrote:
Hi Marc, Tomas, Karl and others,
I noticed some activity on Gerrit regarding the Risc-V based GigaDevice GD32VF103 \
microcontroller: [ http://openocd.zylin.com/#/c/5839/ | \
http://openocd.zylin.com/#/c/5839/ ] I just want to inform all of you that GigaDevice \
forked OpenOCD a couple of days ago: [ \
https://github.com/GigaDevice-Semiconductor/openocd | \
https://github.com/GigaDevice-Semiconductor/openocd ] In their fork, they're adding \
support for their chips. It can be a first step to upstream these fixes to the \
official OpenOCD repo. I'm in contact with some engineers at GigaDevice. They're very \
kind and helpful, so please don't hesitate to post questions/ideas/issues/... on \
their GitHub page.
Kind regards,
Kristof Mulier
On 29/11/2020 16:06, [ mailto:kristof.mulier@telenet.be | kristof.mulier@telenet.be ] \
wrote:
BQ_BEGIN
2. GigaDevice recently forked OpenOCD and applied some fixes/additions to support \
some of their MCUs (see [ https://github.com/GigaDevice-Semiconductor/openocd | \
https://github.com/GigaDevice-Semiconductor/openocd ] ). Maybe it's good to have a \
look at this fork and merge their fixes with yours? In any case, it would be sad if \
part of the OpenOCD community keeps working on GigaDevice MCU support in the official \
OpenOCD repo, and other part of the community (including the GigaDevice engineers) \
does the same work in their own fork. I think it's good to contact GigaDevice to \
discuss this - what do you think? I can help with putting you in contact with the \
right people.
BQ_END
I'm afraid you misunderstand how our project works.
[ http://openocd.org/doc/doxygen/html/patchguide.html | \
http://openocd.org/doc/doxygen/html/patchguide.html ] clearly states: \
------
Submitting patches to the OpenOCD Gerrit server
OpenOCD is to some extent a "self service" open source project, so to contribute, you \
must follow the standard procedures to have the best possible chance to get your \
changes accepted.
-----
Please believe me, we (maintainers) have no time to gather changes from every fork of \
OpenOCD on github and everywhere. And moreover if we did so it would be quite unfair \
to the authors of lots of changes which are already waiting in the gerrit.
So if GidaDevice people want to contribute upstream, they can send changes to gerrit \
as anybody other do (including ST Microelectronics). If they preferred to create a \
fork, it's their business and we can't do anything about it... If you have a contact \
to "the right people" please forward him this mail.
Tom
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
[Attachment #5 (text/html)]
<html><body><div style="font-family: Verdana, Arial, Helvetica, sans-serif; \
font-size: 10pt; color: #000000"><div>Hi Tomas,<br></div><div><br \
data-mce-bogus="1"></div><div><em>> "Please believe me, we (maintainers) have no \
time to gather changes from every fork of OpenOCD on github and everywhere. And \
moreover if we did so it would be quite unfair to the authors of lots of changes \
which are already waiting in the gerrit."</em></div><div><br \
data-mce-bogus="1"></div><div>I didn't realize this before. My apologies. I'll \
contact GigaDevice and explain it to them.</div><div><br \
data-mce-bogus="1"></div><div>About the free GigaDevice boards, are you (and/or some \
of your co-workers) interested?<br data-mce-bogus="1"></div><div><br \
data-mce-bogus="1"></div><div>Kind regards,<br data-mce-bogus="1"></div><div>Kristof \
Mulier<br data-mce-bogus="1"></div><div><br \
data-mce-bogus="1"></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div \
data-marker="__HEADERS__"><b>Van: </b>"openocd-devel" \
<openocd-devel@lists.sourceforge.net><br><b>Aan: </b>"openocd-devel" \
<openocd-devel@lists.sourceforge.net><br><b>Verzonden: </b>Maandag 30 november \
2020 10:50:40<br><b>Onderwerp: </b>Re: [OpenOCD-devel] GigaDevice \
support<br></div><div><br></div><div data-marker="__QUOTED_TEXT__"><div \
class="moz-cite-prefix">Hi Kristof,<br> <br>
On 22/11/2020 11:57, <a href="mailto:kristof.mulier@telenet.be" target="_blank" \
rel="nofollow noopener noreferrer">kristof.mulier@telenet.be</a> wrote:<br> </div>
<blockquote>
<pre class="moz-quote-pre">Hi Marc, Tomas, Karl and others,
I noticed some activity on Gerrit regarding the Risc-V based GigaDevice GD32VF103 \
microcontroller: <a href="http://openocd.zylin.com/#/c/5839/" target="_blank" \
rel="nofollow noopener noreferrer">http://openocd.zylin.com/#/c/5839/</a>
I just want to inform all of you that GigaDevice forked OpenOCD a couple of days ago:
<a href="https://github.com/GigaDevice-Semiconductor/openocd" target="_blank" \
rel="nofollow noopener \
noreferrer">https://github.com/GigaDevice-Semiconductor/openocd</a>
In their fork, they're adding support for their chips. It can be a first step to \
upstream these fixes to the official OpenOCD repo. I'm in contact with some engineers \
at GigaDevice. They're very kind and helpful, so please don't hesitate to post \
questions/ideas/issues/... on their GitHub page.
Kind regards,
Kristof Mulier
</pre>
</blockquote>
<br>
<div class="moz-cite-prefix">On 29/11/2020 16:06,
<a href="mailto:kristof.mulier@telenet.be" target="_blank" rel="nofollow \
noopener noreferrer">kristof.mulier@telenet.be</a> wrote:<br> </div>
<blockquote>
<div><strong>2.</strong> GigaDevice recently forked OpenOCD and
applied some fixes/additions to support some of their MCUs (see
<a href="https://github.com/GigaDevice-Semiconductor/openocd" target="_blank" \
rel="nofollow noopener \
noreferrer">https://github.com/GigaDevice-Semiconductor/openocd</a> ). Maybe it's \
good to have a look at this fork and merge their fixes with yours? In any case, it \
would be sad if part of the OpenOCD community keeps working on GigaDevice MCU \
support in the official OpenOCD repo, and other part of the community
(including the GigaDevice engineers) does the same work in their
own fork. I think it's good to contact GigaDevice to discuss
this - what do you think? I can help with putting you in contact
with the right people.<br>
</div>
<div><br>
</div>
</blockquote>
<br>
I'm afraid you misunderstand how our project works.<br>
<br>
<a href="http://openocd.org/doc/doxygen/html/patchguide.html" target="_blank" \
rel="nofollow noopener \
noreferrer">http://openocd.org/doc/doxygen/html/patchguide.html</a> clearly \
states:<br>
------<br>
<b>Submitting patches to the OpenOCD Gerrit server</b><br>
OpenOCD is to some extent a "self service" open source project, so <b>to
contribute, you must follow the standard procedures</b> to have
the best possible chance to get your changes accepted.<br>
-----<br>
Please believe me, we (maintainers) have no time to gather changes
from every fork of OpenOCD on github and everywhere.<br>
And moreover if we did so it would be quite unfair to the authors of
lots of changes which are already waiting in the gerrit.<br>
<br>
So if GidaDevice people want to contribute upstream, they can send
changes to gerrit as anybody other do<br>
(including ST Microelectronics). If they preferred to create a fork,
it's their business and <span class="VIiyi" lang="en"><span class="JLqJ4b \
ChMk0b">we can't do anything about it...<br>
If you have a </span></span><span class="VIiyi" lang="en"><span \
class="JLqJ4b ChMk0b">contact to "the right people" please forward him this \
mail.<br> <br>
Tom<br>
</span></span>
<br><br>_______________________________________________<br>OpenOCD-devel mailing \
list<br>OpenOCD-devel@lists.sourceforge.net<br>https://lists.sourceforge.net/lists/listinfo/openocd-devel<br></div></div></body></html>
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic