Is xilinx source code license ok with rtems?

[Robert S. Grimes]

Hi Joel,

It looks as though we may be going away from using the Xilinx drivers
after all.  In one sense, that's too bad, in that they seem to be fairly
well written, and designed to work in the BSP layer world.  On the other
hand, writing our own RTEMS drivers and putting them in the RTEMS tree
makes life easier down the road, as it's one less separate code base to
be maintained.  Seems Keith has decided to write a driver without the
Xilinx code, so the point may be mute.  Still, the original question is
important, and it's good to know your thinking on it all.

-Bob

P.S. Answers to your questions below...\

Joel Sherrill wrote:
> What is the code in question used for?
The code is low-level, register-manipulatin' code that fits between an
OS (i.e. RTEMS) network driver and the Xilinx IP.  So it would be
applicable only for a very specific target - the Xilinx parts.  So it
would indeed only be useful for Xilinx parts, which meets the Xilinx
licensing requirements.
> And where do you propose it be located?
I would think the actual Xilinx driver code wouldn't actually be part of
the RTEMS tree; that certainly avoids any legal issues. 
>
> As a practical matter, if it become part of the xilinx BSP and was NOT
> in a position
> to be shared with anything else, it shouldn't be a problem.  No worse
> than using some
> other board specific vendor disclaimed file in a BSP.  But if must be
> clearly hidden
> in a BSP specific directory or (maybe) powerpc/shared/xilinx with a
> BIG WARNING
> file.
Thanks for the "policy" info!
>
> --joel
>
> --joel
>> -Bob
>>
>> Keith Robertson wrote:
>>  
>>> I'm about to write the rtems networking driver for the xilinx temac
>>> 'hard core' emac present in the virtex 4.
>>>
>>> Turns out that xilinx provides a number of drivers intended to be
>>> independent of an RTOS and could be utilised by a rtems adaptor
>>> driver.     From an initial glance through the documentation and
>>> headers it appears this low level driver might be an appropriate fit
>>> with the rtems networking subsystem.  It's probably not hard to
>>> write a layer on top of this rtems code that integrates into the
>>> rtems networking framework.
>>>
>>> I'd like this driver to be included in the proposed virtex ppc bsp. 
>>> So before I go any further I'd like to find out if the license below
>>> is suitable to include in rtems.
>>>
>>> To my eyes, the license seems ok, except possibly for the clause
>>> "soley for use in developing programs and solutions for _xilinx
>>> devices_" (emphasis mine).
>>>
>>> As using this driver _requires_ one to have a xilinx device, this
>>> seems not to be a problem.  However, the rtems source base is
>>> obviously larger than just the one bsp.  Are there any negative
>>> implications here?
>>>
>>> Comments very much appreciated.
>>>
>>> Cheers.
>>>
>>> Keith
>>>
>>> P.S.  Xilinx license follows:
>>>
>>> /******************************************************************************
>>>
>>> *
>>> *       XILINX IS PROVIDING THIS DESIGN, CODE, OR INFORMATION "AS IS"
>>> *       AS A COURTESY TO YOU, SOLELY FOR USE IN DEVELOPING PROGRAMS AND
>>> *       SOLUTIONS FOR XILINX DEVICES.  BY PROVIDING THIS DESIGN, CODE,
>>> *       OR INFORMATION AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE,
>>> *       APPLICATION OR STANDARD, XILINX IS MAKING NO REPRESENTATION
>>> *       THAT THIS IMPLEMENTATION IS FREE FROM ANY CLAIMS OF
>>> INFRINGEMENT,
>>> *       AND YOU ARE RESPONSIBLE FOR OBTAINING ANY RIGHTS YOU MAY
>>> REQUIRE
>>> *       FOR YOUR IMPLEMENTATION.  XILINX EXPRESSLY DISCLAIMS ANY
>>> *       WARRANTY WHATSOEVER WITH RESPECT TO THE ADEQUACY OF THE
>>> *       IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
>>> *       REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF
>>> *       INFRINGEMENT, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
>>> *       FOR A PARTICULAR PURPOSE.
>>> *
>>> *       (c) Copyright 2005-2006 Xilinx Inc.
>>> *       All rights reserved.
>>> *
>>> ******************************************************************************/
>>>
>>> _______________________________________________
>>> rtems-users mailing list
>>> rtems-users at rtems.com
>>> http://rtems.rtems.org/mailman/listinfo/rtems-users
>>>
>>>
>>>       
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.com
>> http://rtems.rtems.org/mailman/listinfo/rtems-users
>>   
>
>