regards,
karthik bala guru
Are you sure u can do this, without breaking the GPL?
Can't be too tightly integrated, that is for sure.
--
Best Regards,
Ulf Samuelsson
u...@a-t-m-e-l.com
This message is intended to be my own personal view and it
may or may not be shared by my employer Atmel Nordic AB
Actually i have not thought of the GPL here.
Could you please tell me in detail.
It would of great helpto me.
Tonnes of thanks in advance,
karthik bala guru.
<bluek...@yahoo.com> skrev i meddelandet
news:1108969221.5...@c13g2000cwb.googlegroups.com...
It doesnt violate GPL, you just have to put the VxWorks source code into GPL
which probably violates the agreement with Wind River.
--
Best Regards
Ulf at atmel dot com
These comments are intended to be my own opinion and they
may, or may not be shared by my employer, Atmel Sweden.
Expecting ur link/doc,
karthik bala guru
Try this: <http://www.gnu.org/copyleft/gpl.html>.
It was the first hit from about 25 million when
Googling for 'GPL'. Please learn to use Google.
--
Tauno Voipio
tauno voipio (at) iki fi
thanx and regards,
karthik bala guru
That is just a logical conclusion of the GPL agreement
and no documentation exists AFAIK.
If you use the arm-linux code and link with VxWorks
then you cannot provide the resulting product
to anyone without releasing the source of everything.
This then includes VxWorks.
There are some limitations.
You can sell a PC with Windows and a Windows GNU compiler
without having to priovide the source of Windows,
but I do not think you can link Vxworks with a BT stack.
If you can have a dynamically linked library with the BT stack,
then you might get away with it.
--
Best Regards,
Ulf Samuelsson
u...@a-t-m-e-l.com
This message is intended to be my own personal view and it
may or may not be shared by my employer Atmel Nordic AB
Did you read the GNU documentation?
You cannot copy the GPL'd protocol stack to
a closed-source system, unless you can get
the VxWorks sources published under GPL.
It is no too probable that anybody wants to
help you to break the licensing limitations.
It seems that the only way out is that you
write a new protocol stack from scratch
(not copying *any* of the Linux one).
Thanks and regards,
karthik bala guru