forked from Imagelibrary/rtems
2003-09-19 Joel Sherrill <joel@OARcorp.com>
* analog.t, bsp_howto.texi, discrete.t, nvmem.t, target.t: Merge from branch.
This commit is contained in:
@@ -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>
|
2003-08-22 Joel Sherrill <joel@OARcorp.com>
|
||||||
|
|
||||||
* adaintr.t, ata.t, target.t: Reconcile differences between CVS trunk
|
* adaintr.t, ata.t, target.t: Reconcile differences between CVS trunk
|
||||||
|
|||||||
@@ -28,11 +28,10 @@ DACs or ADCs on a single card.
|
|||||||
|
|
||||||
There are currently no analog device drivers included in the
|
There are currently no analog device drivers included in the
|
||||||
RTEMS source tree. The information provided in this chapter
|
RTEMS source tree. The information provided in this chapter
|
||||||
is based on drivers developed by OAR Corporation personnel
|
is based on drivers developed for applications using RTEMS.
|
||||||
for applications using RTEMS. It is hoped that this
|
It is hoped that this driver model information can form the
|
||||||
driver model information can form the basis for a standard
|
basis for a standard analog driver model that can be supported
|
||||||
analog driver model that can be supported in future RTEMS
|
in future RTEMS distribution.
|
||||||
distribution.
|
|
||||||
|
|
||||||
@section Major and Minor Numbers
|
@section Major and Minor Numbers
|
||||||
|
|
||||||
|
|||||||
@@ -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
|
||||||
|
|||||||
@@ -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
|
There are currently no discrete I/O device drivers included in the
|
||||||
RTEMS source tree. The information provided in this chapter
|
RTEMS source tree. The information provided in this chapter
|
||||||
is based on drivers developed by OAR Corporation personnel
|
is based on drivers developed for applications using RTEMS.
|
||||||
for applications using RTEMS. It is hoped that this
|
It is hoped that this driver model information can form the
|
||||||
driver model information can form the basis for a standard
|
|
||||||
discrete I/O driver model that can be supported in future RTEMS
|
discrete I/O driver model that can be supported in future RTEMS
|
||||||
distribution.
|
distribution.
|
||||||
|
|
||||||
|
|||||||
@@ -25,12 +25,11 @@ by this class of device driver are:
|
|||||||
@end itemize
|
@end itemize
|
||||||
|
|
||||||
There is currently only one non-volatile device driver included in the
|
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.
|
RTEMS source tree. The information provided in this chapter
|
||||||
The information provided in this chapter is based on drivers developed
|
is based on drivers developed for applications using RTEMS.
|
||||||
by OAR Corporation personnel for applications using RTEMS. It is
|
It is hoped that this driver model information can form the
|
||||||
hoped that this driver model information can form the basis for a standard
|
basis for a standard non-volatile memory driver model that
|
||||||
non-volatile memory driver model that can be supported in future RTEMS
|
can be supported in future RTEMS distribution.
|
||||||
distribution.
|
|
||||||
|
|
||||||
@section Major and Minor Numbers
|
@section Major and Minor Numbers
|
||||||
|
|
||||||
|
|||||||
@@ -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.
|
Otherwise both CPU dependent code and the BSP will have to be written.
|
||||||
|
|
||||||
Regardless of the amount of development required, OAR Corporation
|
This type of development often requires specialized skills. If
|
||||||
offers custom development services to assist RTEMS users.
|
you need help in making these modifications to RTEMS, please
|
||||||
For more information on custom development, training courses, and
|
consider using one of the RTEMS Service Providers. The current
|
||||||
support, contact OAR Corporation at
|
list of these is at @uref{@value{RTEMSHTTPURL}/support.html}.
|
||||||
@uref{http://www.oarcorp.com}.
|
|
||||||
|
|
||||||
|
|
||||||
@section CPU Dependent Executive Files
|
@section CPU Dependent Executive Files
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user