public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
* source code question about confidential datasheet
@ 2008-02-17 15:39 chou.o.ning
  2008-02-17 19:34 ` Gary Thomas
  0 siblings, 1 reply; 2+ messages in thread
From: chou.o.ning @ 2008-02-17 15:39 UTC (permalink / raw)
  To: ecos-devel

Hi, eCos developers

I have porting eCos to some hardware board. As GPL license, I should
deliver source code to eCos community. The question is: the datasheet
of CPU is CONFIDENTIAL, and I need the registers description of
datasheet to write bsp codes to porting.(I did not using the codes
which provided by chip vendor)
If I deliver codes to open source, will I break the law of chip verdor?

Thanks!

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: source code question about confidential datasheet
  2008-02-17 15:39 source code question about confidential datasheet chou.o.ning
@ 2008-02-17 19:34 ` Gary Thomas
  0 siblings, 0 replies; 2+ messages in thread
From: Gary Thomas @ 2008-02-17 19:34 UTC (permalink / raw)
  To: chou.o.ning; +Cc: ecos-devel

chou.o.ning wrote:
> Hi, eCos developers
> 
> I have porting eCos to some hardware board. As GPL license, I should
> deliver source code to eCos community. The question is: the datasheet
> of CPU is CONFIDENTIAL, and I need the registers description of
> datasheet to write bsp codes to porting.(I did not using the codes
> which provided by chip vendor)
> If I deliver codes to open source, will I break the law of chip verdor?

Firstly, in today's world, your vendor is being pretty silly :-(

I am not a lawyer (IANAL), so treat everything I say carefully.
If you are concerned, contact a good Intellectual Property lawyer
before you distribute anything.

I do think if you structure things carefully and don't name
anything so that it will expose the secrets, it will probably be
OK.

Secondly, the GPL only says that you need to distribute the source
code to those to whom you distribute the code (executable, etc).
Presumably those folks would have similar information available
to them as well, so there's no leaking there either.

Finally, in order to port eCos, you *need* to have a GCC port
(there's just too much in eCos that depends on some special
GCC support).  If this exists, how do they handle it since
they'd be dealing with the same sensitive information?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-02-17 19:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-17 15:39 source code question about confidential datasheet chou.o.ning
2008-02-17 19:34 ` Gary Thomas

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).