Re: Anyone really use those opensource CPUs (OR1K, Lattice Mico32, Leon)?

Antti,

In the user guide I pointed to, there is no reference to any agreement.

Your link points to the use agreement. It is not specific to anything.
It has to be specifically stated in each and every document that the
use agreement applies, and how it applies.

I did find one reference to "use within a Xilinx FPGA" in one of the
..pdf marketing documents, but that reference did not provide any
details, nor any restrictions.

I suspect that one .pdf document is not considered binding, or legal, as
it does not refer to any "real" agreement (like the link you provide).

One sentence like "use within a Xilinx FPGA" is more of a desire to keep
the PicoBlaze 'in the family....' than any kind of binding legal use
agreement.

I will go ahead and ask,

Austin

Antti wrote:
On Jul 11, 3:25 pm, austin <aus...@xxxxxxxxxx> wrote:
X-User,

PicoBlaze is offered "as - is", and subsequently has no restrictions on
its use.

It is in the 'spirit' of an open core, as in, we really do not mind
where and how it may be used.

It is also "unsupported" by the Xilinx Support system. If we find
something that is a bug, we will fix it, but we do not offer any
guarantees about its use, or performance like we do for the
MicroBlaze(tm) or PowerPC(tm) processors.

http://www.xilinx.com/bvdocs/userguides/ug129.pdf

Austin

Austin,

it looks like you dont know what you are talking about:

ASFAIK PicoBlaze is under XDL License -
http://www.xilinx.com/bvdocs/appnotes/Design_License.pdf

those it is resctricted for the use in Xilinx devices only.
=> this is not OPEN SOURCE and FREE FOR ANY USE !

so if you dont care in what silicon it is used thats fine,
but officially Xilinx lawers could prevent ASICs with PicoBlaze
inside from being used.

or is there any other way to understand the XDL terms?

Antti
















.

Relevant Pages

  • Last Xilinx Webpack that was big-brother free?
    ... but I tend to cruise through the license agreements ... and EULAs before installing software to make sure I'm not being ... By agreeing to this Agreement, ... Xilinx to use and disclose this information anywhere in the world for ...
    (comp.arch.fpga)
  • Re: Adios, Cingular!
    ... amended as described in this Agreement. ... reference will ALWAYS supercede the Service Agreement. ... It won't, any more than Cingular would be bound to give you 10,000 ... Where did I mention forced performance? ...
    (alt.cellular.cingular)
  • Re: Adios, Cingular!
    ... amended as described in this Agreement. ... inconsistent or additional representations made to you by any of our ... It had to do with a reference to a statute that does not exist by a Cingular ...
    (alt.cellular.cingular)
  • Re: Last Xilinx Webpack that was big-brother free?
    ... and EULAs before installing software to make sure I'm not being ... By agreeing to this Agreement, ... Xilinx to use and disclose this information anywhere in the world for ... computer to leak information out into the world beyond my control. ...
    (comp.arch.fpga)
  • Re: dbdebunk Quote of Week comment
    ... I think we are in basic agreement. ... and therefore a container. ... as "retrieving a row" rather than "retrieving some row uniquely specified by ... "the conventional name of an entity catalogued in the reference table". ...
    (comp.databases.theory)