Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] LPC2103 in IAR EWARM

2006-01-17 by Tom Walsh

Paul Curtis wrote:

>Tom, 
>
>  
>
>>>With respect - if they are not distributing them yet - 
>>>      
>>>
>>neither should you.
>>    
>>
>>>I presume they are copyrighted?
>>>
>>>      
>>>
>>Probably patented too...  Seems that a number of people slap a 
>>boilerplate copyright header into everything they do, even 
>>trivial code, 
>>or stuff that isn't theirs.  e.g. header files describing register 
>>locations and bit values / name.  In the case of the header 
>>files, they 
>>are using the exact verbage as Philips.
>>
>>Now how can you justify asserting that you have a copywrite 
>>on something 
>>that isn't yours???  Apparently Microsoft is not the only one to use 
>>Fear, Uncertainty and Doubt?!
>>    
>>
>
>All our header files are generated from XML descriptions and those are
>also used in the debugger and build system.  As to copyright, the person
>who typed in the names does it for the company they are working for and,
>as such, it is part of their job to ensure that even trivial things are
>copyrighted.  Given the large number of registers that some ARM chips
>have, this is not a trivial task.  Hence, a copyright is an essential
>part of software and product development to ensure that a competitor
>does not simply steal your work.
>
>  
>
Well, apparently you went to a different school than I did.  Copyright 
can only be asserted on an original work, simply reformatting an 
existing work does not automagically create a copyright.  Nor does 
"sweat" justify assigning a copyright.  Respectfully, it is my opinion 
that you spend some time looking into copyright practice.

TomW

-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.