RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

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

Browse Source 
* analog.t, bsp_howto.texi, discrete.t, nvmem.t, target.t: Merge from
	branch.
This commit is contained in:
Joel Sherrill
2003-09-19 18:05:20 +00:00
parent 98bc9752ce
commit ac9ddffab1
6 changed files with 21 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/bsp_howto/ChangeLog
View File

@@ -1,3 +1,8 @@
2003-09-19 Joel Sherrill <joel@OARcorp.com>
* analog.t, bsp_howto.texi, discrete.t, nvmem.t, target.t: Merge from
branch.
2003-08-22 Joel Sherrill <joel@OARcorp.com>
* adaintr.t, ata.t, target.t: Reconcile differences between CVS trunk

9
doc/bsp_howto/analog.t
View File

@@ -28,11 +28,10 @@ DACs or ADCs on a single card.
There are currently no analog device drivers included in the
RTEMS source tree. The information provided in this chapter
is based on drivers developed by OAR Corporation personnel
for applications using RTEMS. It is hoped that this
driver model information can form the basis for a standard
analog driver model that can be supported in future RTEMS
distribution.
is based on drivers developed for applications using RTEMS.
It is hoped that this driver model information can form the
basis for a standard analog driver model that can be supported
in future RTEMS distribution.
@section Major and Minor Numbers

1
doc/bsp_howto/bsp_howto.texi
View File

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

5
doc/bsp_howto/discrete.t
View File

@@ -28,9 +28,8 @@ on the notion of reading bitfields from the card.
There are currently no discrete I/O device drivers included in the
RTEMS source tree. The information provided in this chapter
is based on drivers developed by OAR Corporation personnel
for applications using RTEMS. It is hoped that this
driver model information can form the basis for a standard
is based on drivers developed for applications using RTEMS.
It is hoped that this driver model information can form the
discrete I/O driver model that can be supported in future RTEMS
distribution.

11
doc/bsp_howto/nvmem.t
View File

@@ -25,12 +25,11 @@ by this class of device driver are:
@end itemize
There is currently only one non-volatile device driver included in the
RTEMS source tree and it does not adhere to this device driver model.
The information provided in this chapter is based on drivers developed
by OAR Corporation personnel for applications using RTEMS. It is
hoped that this driver model information can form the basis for a standard
non-volatile memory driver model that can be supported in future RTEMS
distribution.
RTEMS source tree. The information provided in this chapter
is based on drivers developed for applications using RTEMS.
It is hoped that this driver model information can form the
basis for a standard non-volatile memory driver model that
can be supported in future RTEMS distribution.
@section Major and Minor Numbers

10
doc/bsp_howto/target.t
View File

@@ -102,12 +102,10 @@ be augmented. After this is done, development of the new BSP can proceed.
Otherwise both CPU dependent code and the BSP will have to be written.
Regardless of the amount of development required, OAR Corporation
offers custom development services to assist RTEMS users.
For more information on custom development, training courses, and
support, contact OAR Corporation at
@uref{http://www.oarcorp.com}.
This type of development often requires specialized skills. If
you need help in making these modifications to RTEMS, please
consider using one of the RTEMS Service Providers. The current
list of these is at @uref{@value{RTEMSHTTPURL}/support.html}.
@section CPU Dependent Executive Files