PPC405GPr with RTEMS + Support? (+ License talk)

[Joel Sherrill <joel@OARcorp.com>]

Smith, Gene wrote:
> Joel Sherrill <joel at OARcorp.com> wrote, On 8/5/2004 4:07 PM:
> 
>> I don't need a lawyer to know that I wouldn't touch the IBM code and
>> you are spouting the party line on the Linux kernel.  All that ranting
>> on my part has paid off. :)
> 
> 
> Don't know about your "ranting" but seem obvious from read of the RTEMS 
> and GPL licenses that you can't derive from GPL code that is not 
> initially released/copyrighted with the RTEMS addendum, unless you 
> distribute to customers your whole project (rtems code + application + 
> GPL derived driver code) all as pure GPL.
> 
> So I should treat the IBM code as radioactive? Guess the IBM wording 
> kind of implies that IBM could someday claim a patent on the code. Plus 
> the thing about $1k libility sounds weird. I can see you would not want 
> this verbage in the rtems tree, as using it would require.

I would not want a project potentially on the hook for the $1K either.
Weird terms.

>> NetBSD has a driver for the 405 EMAC in src/sys/arch/powerpc/ibm4xx
>> based upon my last checkout of their source.
>> The dev subdirectory has if_emacs* which should be exactly what you
>> want as a starting point.  There are multiple people on the list who
>> have transformed BSD network drivers into RTEMS drivers.
> 
> 
> Thanks for the pointer to netbsd. I hadn't looked there. However, 
> if_emacs.c has this statement in its starting comments:
> 
> 3. All advertising materials mentioning features or use of this software
>  * must display the following acknowledgement:
>  * This product includes software developed for the NetBSD Project by
>  * Wasabi Systems, Inc.
> 
> I think this is the dreaded "advertising clause." I believe I have also 
> seen similar words in the RTEMS bsd stack files. Would this requirment 
> somehow be superceded by the overarching NetBSD or RTEMS license? Or do 
> you really have to put something on your device label or manual saying 
> "OAR RTMES + Wasabi NetBSD + U.Calif BSD Inside"?

Ralf is right.. I should have pointed you to FreeBSD so there wasn't
this clause.

The U. Calif does not require the advertising clause anymore.  If it
is in the code, it can be ignored. There is a reference to that
somewhere on the net.  I only see one file in the libnetworking
source that has another advertising claim...

libc/ether_addr.c:
  * 3. All advertising materials mentioning features or use of this software
  *    must display the following acknowledgement:
  *      This product includes software developed by Bill Paul.


Ralf.. as of June 6, the current FreeBSD code still had this in it.
What is their policy again?


You don't have to mention OAR/RTEMS at all.

Unfortunately for the WASABI code, I think your reading is correct.
Somewhere

> The NetBsd license page
> http://www.netbsd.org/Goals/redistribution.html
> says this:
> 2. Redistributions in binary form must reproduce the above copyright
>    notice, this list of conditions and the following disclaimer in the
>    documentation and/or other materials provided with the distribution.
> 
> What does it all mean?  :-(

We have to be ever vigilant when using code from other sources.  I think
the RTEMS TCP/IP stack is OK minus the libc/ether_addr.c above which
we need to investigate.

> -gene
> 
> 
> 
> 
> 
> 
> 
>>
>>
>>> -gene
>>>
>>>
>>>
>>>
>>
>>
>>


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
    Support Available             (256) 722-9985