Imagelibrary/rtems
1
0
Fork 1
mirror of https://gitlab.rtems.org/rtems/rtos/rtems.git synced 2025-12-05 15:15:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

2003-09-19 Joel Sherrill <joel@OARcorp.com>

Browse Source 
* FAQ.texi, basic.t, build45.t, entry, tools.t: Merge from branch.
This commit is contained in:
Joel Sherrill
2003-09-19 18:05:31 +00:00
parent ac9ddffab1
commit 7962e86e93
6 changed files with 60 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/FAQ/ChangeLog
View File

@@ -1,3 +1,7 @@
2003-09-19 Joel Sherrill <joel@OARcorp.com>
* FAQ.texi, basic.t, build45.t, entry, tools.t: Merge from branch.
2003-05-22 Ralf Corsepius <corsepiu@faw.uni-ulm.de> 2003-05-22 Ralf Corsepius <corsepiu@faw.uni-ulm.de>
* build45.t: Fix typo (config.long). * build45.t: Fix typo (config.long).

1
doc/FAQ/FAQ.texi
View File

@@ -21,6 +21,7 @@
@include version.texi @include version.texi
@include common/setup.texi @include common/setup.texi
@include common/rtems.texi
@ifset use-ascii @ifset use-ascii
@dircategory RTEMS On-Line Manual @dircategory RTEMS On-Line Manual

34
doc/FAQ/basic.t
View File

@@ -138,43 +138,55 @@ source code was available and royalties were paid.
In other words, RTEMS was open source before open source was cool. In other words, RTEMS was open source before open source was cool.
Since the initial release to the world, the RTEMS Community has
grown enormously and contributed significantly to RTEMS. Important
additions such as the TCP/IP stack, FAT filesystem, multiple ports,
device drivers, and most BSPs have come from users like yourself.
@section Are there no similar commercial products? @section Are there no similar commercial products?
Yes, but not all are based on standards and the open source philosophy. Yes, but not all are based on standards and the open source philosophy.
@section How can I get RTEMS? @section How can I get RTEMS?
RTEMS is distributed by OAR Corporation via the Internet. Point your RTEMS is distributed from @uref{@value{RTEMSHTTPURL},@value{RTEMSHTTPURL}}.
This is a server dedicated to the RTEMS Project which was donated by and
hosted by @uref{http://www.OARcorp.com,OAR Corporation} to provide
a focal point for all RTEMS activities. Point your
favorite browser at the following URL and following the link: favorite browser at the following URL and following the link:
@c this version should work @uref{@value{RTEMSHTTPURL},@value{RTEMSHTTPURL}}
@c @set OAR-URL http://www.OARcorp.com
@c @uref{@value{OAR-URL},@value{OAR-URL}} But if you are already reading this, you probably already found it. :)
@uref{http://www.OARcorp.com,http://www.OARcorp.com}
@section What about support? @section What about support?
OAR Corporation provides numerous services for RTEMS including support, RTEMS development and support services are available from a number
training, and custom development. of firms. See
@uref{@value{RTEMSHTTPURL}/support.html,@value{RTEMSHTTPURL}/support.html}
for the current list of RTEMS service providers.
Remember that RTEMS maintenance is funded by users. If you are
using RTEMS on a commercial project, please get support.
@section Are there any mailing lists? @section Are there any mailing lists?
The primary RTEMS mailing list is @code{rtems-users@@oarcorp.com}. This The primary RTEMS mailing list is @code{@value{RTEMSUSERS}}. This
list is for general RTEMS discussions, questions, design help, advice, list is for general RTEMS discussions, questions, design help, advice,
etc.. Subscribe by sending an empty mail etc.. Subscribe by sending an empty mail
message to @code{rtems-users-subscribe@@OARcorp.com}. This message to @code{@value{RTEMSUSERSSUBSCRIBE}}. This
mailing list is archived at: mailing list is archived at:
@example @example
http://www.oarcorp.com/rtems/maillistArchives/rtems-users http://www.oarcorp.com/rtems/maillistArchives/rtems-users
@end example @end example
The @code{rtems-snapshots@@oarcorp.com} mailing list is for those The @code{@value{RTEMSSNAPSHOTS}} mailing list is for those
interested in taking a more active role in the design, development, interested in taking a more active role in the design, development,
and maintenance of RTEMS. Discussions on this list tend to focus and maintenance of RTEMS. Discussions on this list tend to focus
on problems in the development source, design of new features, problem on problems in the development source, design of new features, problem
reports, etc.. Subscribe by sending an empty mail reports, etc.. Subscribe by sending an empty mail
message to @code{rtems-snapshots-subscribe@@OARcorp.com}. message to @code{@value{RTEMSSNAPSHOTSSUBSCRIBE}}.
mailing list is archived at: mailing list is archived at:
@example @example

10
doc/FAQ/build45.t
View File

@@ -72,7 +72,7 @@ Native Cygwin binaries should be available at Cygnus.
GNU-Toolchain binaries (gcc, binutils etc.) for Linux and patches required GNU-Toolchain binaries (gcc, binutils etc.) for Linux and patches required
to build them from source are available from to build them from source are available from
@uref{ftp://ftp.oarcorp.com,OAR Corporation}. @uref{@value{RTEMSFTPURL},the RTEMS ftp site}.
@section Issues when building RTEMS @section Issues when building RTEMS
@@ -154,8 +154,8 @@ prefix, eg. i386-rtems-gcc, m68k-rtems-ld are target tools.
Host tools are supposed not to be prefixed. Host tools are supposed not to be prefixed.
e.g.: cc, ld, gcc, autoconf, automake, aclocal etc. e.g.: cc, ld, gcc, autoconf, automake, aclocal etc.
If using OAR Corporation's rpms for the toolchain, simply prepend If using the pre-built tool binaries provided by the RTEMS project,
@code{/opt/rtems/bin} to @code{$PATH}. simply prepend @code{@value{RTEMSPREFIX}} to @code{$PATH}.
@subsection Can I build RTEMS Canadian Cross? @subsection Can I build RTEMS Canadian Cross?
@@ -411,8 +411,8 @@ have been adapted to autoconf >= 2.50 demands.
Several possibilities (In decreasing preference): Several possibilities (In decreasing preference):
@itemize @bullet @itemize @bullet
@item File a bug report at @uref{http://www.oarcorp.com/cgi-bin/gnatsweb.pl,OAR's GNAT} @item File a bug report at @uref{@value{RTEMSGNATS},RTEMS's GNATS}
@item Send an email to @uref{mailto:rtems-bugs@@OARcorp.com,rtems-bugs@@OARcorp.com} @item Send an email to @uref{mailto:@value{RTEMSBUGS},@value{RTEMSBUGS}}
@item Report your problem to one of the RTEMS mailing lists @item Report your problem to one of the RTEMS mailing lists
(Cf. @ref{Are there any mailing lists?}). (Cf. @ref{Are there any mailing lists?}).
@end itemize @end itemize

12
doc/FAQ/entry
View File

@@ -29,8 +29,8 @@ POSIX 1003.1b support, and file system support. It also includes optional
debug aids like stack overflow and heap integrity checking. debug aids like stack overflow and heap integrity checking.
RTEMS is built using GNU autoconf and can be built on any host supporting RTEMS is built using GNU autoconf and can be built on any host supporting
the GNU tools including Linux, FreeBSD, NetBSD, Solaris, and MS-Windows to the GNU tools including GNU/Linux, FreeBSD, NetBSD, Solaris, and MS-Windows
name but a few. The current RTEMS release supports the following CPU to name but a few. The current RTEMS release supports the following CPU
families: families:
Motorola m680x0, m683xx, and ColdFire Motorola m680x0, m683xx, and ColdFire
@@ -47,13 +47,13 @@ families:
There are over 35 Board Support Packages included with RTEMS including There are over 35 Board Support Packages included with RTEMS including
BSPs for a standard PC as well as the SPARC, MIPS, PowerPC simulators BSPs for a standard PC as well as the SPARC, MIPS, PowerPC simulators
included with gdb. There are included with gdb. There are numerous BSPs for CPUs targetting the
numerous BSPs for CPUs targetting the embedded market such as the Motorola embedded market such as the Motorola m683xx, ppc4xx, and mpc8xx series
m683xx, ppc4xx, and mpc8xx series which support the on-CPU peripherals. which support the on-CPU peripherals.
WWW: WWW:
@uref{http://www.OARcorp.com} @uref{http://www.rtems.com}
E-mail: E-mail:

22
doc/FAQ/tools.t
View File

@@ -13,7 +13,7 @@ in a non-language specific way.
@section What is GNU? @section What is GNU?
Take a look at @uref{http://www.gnu.org} for information on the GNU Project. Take a look at @uref{http://www.gnu.org,http://www.gnu.org} for information on the GNU Project.
@section How do I generate a patch? @section How do I generate a patch?
@@ -49,3 +49,23 @@ in the two source files. The GNU open-source packages usually have
UNIX style CR/LF. If you edit on a Windows platform, the line UNIX style CR/LF. If you edit on a Windows platform, the line
terminators may have been transformed by the editor into Windows terminators may have been transformed by the editor into Windows
style. style.
@section How do I apply a patch?
Patches generated with the @code{diff} program are fed into the
@code{patch} program as follows:
@example
patch -p1 <PATCHFILE
@end example
where the options are:
@itemize @bullet
@item -pNUM tells @code{patch} to strip off NUM slashes from the
pathname.
@end itemize
If @code{patch} prompts for a file to patch, you may need to adjust NUM.