* How should a new internally developed board be handled?
@ 2012-06-08 14:48 Jerry Kirk
2012-06-15 12:50 ` Jerry Kirk
0 siblings, 1 reply; 2+ messages in thread
From: Jerry Kirk @ 2012-06-08 14:48 UTC (permalink / raw)
To: barebox
Our company is developing a new board for the i.MX35 series
for use in various internal products. We do not expect to
ever "sell" this board on the open market.
We recognize the "public" license and are willing to release
any modifications so that others might learn from our changes
in order to improve their systems.
In this case, is it appropriate for me to begin submitting
patches to define our new (internal only) board and it's
configuration? It would certainly be easier if our changes
were in the tree as we migrate through various versions of
barebox.
Thanks,
Jerry
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: How should a new internally developed board be handled?
2012-06-08 14:48 How should a new internally developed board be handled? Jerry Kirk
@ 2012-06-15 12:50 ` Jerry Kirk
0 siblings, 0 replies; 2+ messages in thread
From: Jerry Kirk @ 2012-06-15 12:50 UTC (permalink / raw)
To: barebox
Still looking for some more information on this topic...
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-06-15 12:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-08 14:48 How should a new internally developed board be handled? Jerry Kirk
2012-06-15 12:50 ` Jerry Kirk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox