Hierarchical Navigation

HOME

SUPPORT
- PRODUCT SUPPORT
  - ROUTERS
    - CISCO 1000 SERIES CONNECTED GRID ROUTERS
      - Licensing Information

Open Source Used In Connected Grid WiMAX Module for CGR 1000

This document contains the licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of the source code to which you are entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at external-opensource-requests@cisco.com.

In your requests please include the following reference number 78EE117C99-38292554

1.1 Ecos 2.0

1.1.1 Available under license

1.1 Ecos 2.0

1.1.1 Available under license :

The eCos license version 2.0
This file is part of eCos, the Embedded Configurable Operating System.
Copyright (C) 1998, 1999, 2000, 2001, 2002 Red Hat, Inc.
eCos is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software Foundation;
either version 2 or (at your option) any later version.

eCos is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with eCos;
if not, write to the Free Software Foundation, Inc., 51 Franklin St,
Fifth Floor, Boston, MA 02110-1301 USA.

As a special exception, if other files instantiate templates or use macros or
inline functions from this file, or you compile this file and link it with other
works to produce a work based on this file, this file does not by itself cause
the resulting work to be covered by the GNU General Public License.
However the source code for this file must still be made available
in accordance with section (3) of the GNU General Public License.

This exception does not invalidate any other reasons why a work based
on this file might be covered by the GNU General Public License.

Alternative licenses for eCos may be arranged by contacting Red Hat, Inc.
at http://sources.redhat.com/ecos/ecos-license/ -------------------------------------------

####ECOSGPLCOPYRIGHTEND####

-----------------------------------------------------------------------------------------

GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and
modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type 'show w'. This is free software, and you are welcome to redistribute it under certain conditions; type 'show c' for details. The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than 'show w' and 'show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program 'Gnomovision' (which makes passes at compilers) written by James Hacker.

, 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.

GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Preamble

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

The precise terms and conditions for copying, distribution and
modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

NO WARRANTY

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

eCos Host-side Software
=======================

This README file only describes the eCos host-side software. For
details of the eCos target-side software or the required toolchains,
please see other documentation. A good starting point is
http://sources.redhat.com/ecos

There are two categories of host-side software. The host subdirectory
contains generic software, primarily related to the eCos configuration
technology. All eCos users will need to use some of this technology to
configure and build eCos, either using pre-built binaries or by
building the host-side software from source. The generic software
should be portable to a wide range of host platforms.

There is also package-specific host-side software. Much of this is I/O
related. For example the generic USB-slave package contains some
programs related to testing; a test application is run on a target
with suitable USB slave-side hardware, and needs to interact with
another program running on the USB host; the latter is
package-specific host-side software and can be found in the
subdirectory packages/io/usb/slave. Code like this may have
significant platform dependencies and may only work on a single
platform or on a small number of platforms. There may also be
special requirements, for example it may be necessary to install some
programs suid root so that they have appropriate access to the
hardware.

The host subdirectory includes the following:

infra/
This is an implementation of the eCos infrastructure that can be
used on the host-side, and provides assertion, tracing and
testcase support.

NOTE: the eCos infrastructure facilities are not especially
well-suited to host-side development, in particular they are not
C++-oriented. There are plans to remove the current infrastructure
completely and replace it with something more suitable. People
planning new projects should be aware of this, and may wish to
avoid using the current infrastructure.

libcdl/
The CDL library lies at the heart of the eCos configuration
technology.

tools/configtool/
The sources to the various configuration tools can be found here.

tools/configtool/common/common/
Contains sources related to makefile generation, shared by the
command line and graphical tools.

tools/configtool/standalone/common/
Contains the command line ecosconfig tool.

tools/configtool/standalone/wxwin/
Contains sources for the wxWindows-based, Linux and Windows graphical
configuration tool. The Windows version can currently only be
built with Visual C++, not with cygwin g++.

tools/configtool/common/win32/
tools/configtool/standalone/win32/
Contains sources for the older, MFC-based, Windows-only graphical
configuration tool. Again this can currently only be built with
Visual C++.

The two graphical configuration tools have their own build procedures,
described in tools/configtool/standalone/wxwin/ReadMe and
tools/configtool/standalone/win32/ReadMe respectively.

Package-specific host-side code lives in the host subdirectory of the
appropriate package, for example packages/io/usb/slave/

/host.
Most packages only provide target-side code and hence will not have a
host subdirectory. Users can install various packages from a variety
of sources, and where a package does have host-side software the
package documentation should be consulted for further information.

Installing on Linux, Other Unix Systems, and Cygwin
---------------------------------------------------

Both generic host-side software (infra, libcdl and ecosconfig) and
package-specific software can be built with the conventional
"configure/make/make install" sequence. However the code does not
conform fully to GNU coding standards so some operations such as "make
dist" are not supported. There is limited support for DejaGnu-based
testing.

Much of the host-side software has a dependency on Tcl. This is not
supplied with the sources since many users will already have a
suitable installation, for example it is shipped as standard with all
major Linux distributions. The generic host-side software should work
with any release of Tcl from 8.0 onwards. The package-specific
software requires a more recent version, 8.3 or later. If no suitable
Tcl installation is available then the configure step will still
succeed but some of the package-specific software will not be built.

There are two main approaches to building the host-side software:

1) build the generic and the package-specific code in one build tree.
This uses the top-level configure script. The script automatically
invokes the configure script in the main host subdirectory. In
addition it searches the packages hierarchy for host subdirectories
containing their own configure scripts and will invoke those.

Note: the search for host subdirectories happens during configure
time, not during the make. If new packages with host-side code are
added to the repository then it will be necessary to re-run the
toplevel configure script.

2) build the generic code in one build tree, using the configure
script in the toplevel's host subdirectory. Then build some or all
of the package-specific code in separate build trees, using the
configure scripts in each package's host subdirectory.

The first approach is generally simpler. However some of the
package-specific code requires special installation, for example a
program may have to be installed suid root so that it has the right
privileges to access hardware, and hence the "make install" step has
to be run by the superuser. Also some of the package-specific code is
rather specialized and may be of no interest to many users. For
example, the USB testing code is only useful when developing
USB-based applications. Hence some users may prefer the second
approach, building just the generic code and a subset of the
package-specific code.

It is necessary to use a separate build tree rather than build
directly in the source tree. This is enforced by the configure scripts.

$ mkdir build
$ cd build

The next step is to run the desired configure script. To build all
the host-side software this means the toplevel configure script:

/configure

Alternatively to build just the generic host-side software, use the configure script in the host subdirectory. $ mkdir host $ cd host $

/host/configure

Or, to build just one package's host-side code: $ mkdir -p packages/io/usb/slave/current/host $ cd packages/io/usb/slave/current/host $

/packages/io/usb/slave/current/host/configure

(It is not actually necessary to use the same directory structure in the build tree as in the source tree, but doing so can avoid confusion). A list of all the command-line options can be obtained by running "configure --help". The most important ones are as follows: 1) --prefix. This can be used to specify the location of the install tree, defaulting to /usr/local, so the ecosconfig program ends up in /usr/local/bin/ecosconfig and the CDL library ends up in /usr/local/lib/libcdl.a. If an alternative location is preferred this can be specified with --prefix, for example: $

/configure --prefix=/usr/local/ecos

2) --enable-debug. By default all assertions and tracing are disabled. When debugging any of the generic host-side software these should be enabled. Some package-specific code may not have any extra debug support, in which case --enable-debug would be ignored. $

/configure --enable-debug It is also possible to control most of the assertion and tracing macros at a finer grain. This is intended mainly for use by the developers. --disable-asserts disable all assertions --disable-preconditions disable a subset of the assertions --disable-postconditions disable a subset of the assertions --disable-invariants disable a subset of the assertions --disable-loopinvariants disable a subset of the assertions --disable-tracing disable tracing --disable-fntracing disable function entry/exit tracing 3) --with-tcl=

--with-tcl-version=

The host-side tools have a dependency on Tcl, which is not supplied with the sources because many people will already have a suitable installation. Specifically it is necessary to have the header file tcl.h and appropriate libraries such that -ltcl will work - this can involve either static or shared libraries. Some tools may require Tk as well as Tcl. Unfortunately there is considerable variation in Tcl installations. In theory all Tcl installations have a file tclConfig.sh which defines exactly how to compile and link code that uses Tcl, and Tk has a similar file tkConfig.sh. The eCos configure scripts look for these files, first in $(prefix)/lib, then in /usr/lib. If the system already has a Tcl installation in /usr then the configure script will automatically find /usr/lib/tclConfig.sh and it is not necessary to pass additional options when configuring the eCos host-side software. Alternatively, if for example you have installed a more recent version of Tcl/Tk in the same place that you want to install the eCos software, e.g. /usr/local, then $(prefix)/lib/tclConfig.sh will be read in. It is also possible that a more recent version of Tcl has been installed in a different location. For example, you may wish to install the eCos host tools in /opt/ecos but use a version of Tcl installed in /usr/local. The eCos configure scripts need to be told explicitly where to look for the Tcl: $

/configure --with-tcl=/usr/local ... Some systems, for example Debian Linux 3.0, do not install tclConfig.sh in /usr/lib because that makes it more difficult to have several different versions of Tcl installed at the same time. Instead tclConfig.sh is found in a versioned directory such as /usr/lib/tcl8.3. Since several versions may be installed the desired one must be specified explicitly. $

/configure --with-tcl-version=8.3 The --with-tcl and --with-tcl-version options are combined to give a search path:

/lib/tclConfig.sh

/lib/tcl

/tclConfig.sh

/lib/tclConfig.sh

/lib/tcl

/tclConfig.sh /usr/lib/tclConfig.sh /usr/lib/tcl

/tclConfig.sh If tclConfig.sh cannot be found in any of these places then it is assumed that Tcl has not been properly installed and the eCos configure script will fail. The --with-tcl and --with-tcl-version are also used to give a search path for tkConfig.sh

/lib/tkConfig.sh

/lib/tk

/tkConfig.sh

/lib/tkConfig.sh

/lib/tk

/tkConfig.sh /usr/lib/tkConfig.sh /usr/lib/tk

/tkConfig.sh Again, the configure scripts must be able to find tkConfig.sh Once tclConfig.sh and tkConfig.sh have been found and read in, the eCos configure scripts should have all the information needed to compile and link code that uses Tcl. First the location of key headers such as

is needed. A tclConfig.sh file may define TCL_INC_DIR to give a specific location, otherwise the header files should be in $(TCL_PREFIX)/include. If

cannot be found then the eCos configure scripts will fail. Next it is necessary to work out how to link applications with Tcl. This information should be provided by a tclConfig.sh variable TCL_LIB_SPEC. Unfortunately not all Tcl installations set this, for example the cygwin Tcl 8.4 release. If TCL_LIB_SPEC is not defined then instead the configure script will look for a library libtcl

.a, where

is specified using --with-tcl-version, then for a library libtcl.a Following the configure step the build tree should be set up correctly. All that remains is the actual build and install: $ make $ make install This should result in an ecosconfig executable, plus appropriate libraries and header files. If the install prefix is a system location, for example /usr/local/, then "make install" will normally require root privileges. Also some of the package-specific software has special installation requirements, for example programs that need to be installed suid root, and this will also need root privileges. Installing with Visual C++ -------------------------- Under Windows it is possible to build the generic host-side software (infra, libcdl and ecosconfig) with Visual C++ but this is deprecated. Building with g++ under cygwin is preferred. It is still necessary to run the configure script and a suitable make utility. That requires a shell and a Unix-like environment, as provided by cygwin. The Visual C++ compiler cl.exe needs to be on the shell's search path, and some environment variables such as INCLUDE and LIB may need to be set to point at the Visual C++ installation - the details may vary depending on the version of the compiler. Then the configure command should be run like this: $ CC=cl CXX=cl

/host/configure

Note that the path should be a cygwin path: cygwin mount points are accepted and forward slashes should be used. The various configure scripts now detect that Visual C++ should be used, and adapt accordingly. Depending on what cygwin mount points are set up, /usr/local may or may not be an appropriate install location for VC++ applications. If not, the install location should be specified with --prefix: $ CC=cl CXX=cl

/configure --prefix=

It is also necessary to use the right version of Tcl. For a VC++ build the cygwin release of Tcl should not be used. Instead a suitable prebuilt Tcl package can be obtained from http://www.tcl.tk/. It is necessary to tell the configure script where this has been installed, for example: $ CC=cl CXX=cl

/configure --prefix=

\ --with-tcl=/cygdrive/d/local/scriptics/Tcl/tcl8.1

The library name will be of the form tcl81.lib, and there will not be a symbolic link from tcl.lib to the appropriate version. It will be necessary to specify the Tcl version explicitly since the default version is currently 8.0. $ CC=cl CXX=cl

/configure --prefix=

\ --with-tcl=/d/local/scriptics/Tcl/tcl8.1 --with-tcl-version=81

Following a successful configure, the tools can be built and installed in the normal fashion: $ make $ make install More Information ================ Please see the eCos web site, http://sources.redhat.com/ecos/, for further details. This includes the FAQ, a form for reporting problems, and details of the various mailing lists (http://sources.redhat.com/ecos/intouch.html) At the time of writing there are no separate mailing lists for the eCos host-side sources, the main mailing list ecos-discuss@sources.redhat.com should be used instead. //####COPYRIGHTBEGIN#### // //---------------------------------------------------------------------------- // Copyright (C) 2002 Bart Veer // Copyright (C) 2000, 2001 Red Hat, Inc. // // This file is part of the eCos host tools. // // This program is free software; you can redistribute it and/or modify it // under the terms of the GNU General Public License as published by the Free // Software Foundation; either version 2 of the License, or (at your option) // any later version. // // This program is distributed in the hope that it will be useful, but WITHOUT // ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or // FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for // more details. // // You should have received a copy of the GNU General Public License along with // this program; if not, write to the Free Software Foundation, Inc., // 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. // // ---------------------------------------------------------------------------- // //####COPYRIGHTEND####

The files in this directory and elsewhere which refer to this LICENCE
file are part of JFFS2, the Journalling Flash File System v2.

	Copyright (C) 2001-2003 Red Hat, Inc.

JFFS2 is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2 or (at your option) any later 
version.

JFFS2 is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
for more details.

You should have received a copy of the GNU General Public License along
with JFFS2; if not, write to the Free Software Foundation, Inc.,
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.

As a special exception, if other files instantiate templates or use
macros or inline functions from these files, or you compile these
files and link them with other works to produce a work based on these
files, these files do not by themselves cause the resulting work to be
covered by the GNU General Public License. However the source code for
these files must still be made available in accordance with section (3)
of the GNU General Public License.

This exception does not invalidate any other reasons why a work based on
this file might be covered by the GNU General Public License.

For information on obtaining alternative licences for JFFS2, see 
http://sources.redhat.com/jffs2/jffs2-licence.html


	$Id: LICENCE,v 1.2 2003/10/04 08:33:05 dwmw2 Exp $

Copyright 2004, 2005 Aaron Voisine 
   
   
    
    

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

The Microwindows, Nano-X, and BOGL software are licensed under the MPL,
as specified below.  Alternatively, the software can be converted to
the GNU General Public License, Version 2.

/* 
 * The contents of this file are subject to the Mozilla Public License
 * Version 1.1 (the "License"); you may not use this file except in
 * compliance with the License. You may obtain a copy of the License at
 * http://www.mozilla.org/MPL/
 * 
 * Software distributed under the License is distributed on an "AS IS"
 * basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
 * License for the specific language governing rights and limitations
 * under the License.
 * 
 * The Original Code is MicroWindows.
 * 
 * The Initial Developer of the Original Code is Greg Haerr.
 * Portions created by Greg Haerr are Copyright (C) 1999
 * Greg Haerr 
   
   
    
    . All Rights Reserved.
 * 
 * Contributor(s):
 * 
 * Alternatively, the contents of this file may be used under the terms
 * of the GNU General Public license (the  "[GNU] License"), in which case the
 * provisions of [GNU] License are applicable instead of those
 * above.  If you wish to allow use of your version of this file only
 * under the terms of the [GNU] License and not to allow others to use
 * your version of this file under the MPL, indicate your decision by
 * deleting  the provisions above and replace  them with the notice and
 * other provisions required by the [GNU] License.  If you do not delete
 * the provisions above, a recipient may use your version of this file
 * under either the MPL or the [GNU] License.
 */

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries.To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Cisco 1000 Series Connected Grid Routers

Open Source Used In Connected Grid WiMAX Module for CGR 1000

Hierarchical Navigation

Open Source Used In Connected Grid WiMAX Module for CGR 1000

In your requests please include the following reference number 78EE117C99-38292554

Contents

1.1 Ecos 2.0

1.1.1 Available under license :

Enterprise Networks

Information For

Industries

Marketplace

Contacts

Support

Communities

Video Portal

About Cisco

Careers

Programs