Changeset c4da705 in rtems-docs
- Timestamp:
- 01/11/19 11:45:30 (5 years ago)
- Branches:
- 5, master
- Children:
- c098290
- Parents:
- b5014fe
- git-author:
- Sebastian Huber <sebastian.huber@…> (01/11/19 11:45:30)
- git-committer:
- Sebastian Huber <sebastian.huber@…> (01/14/19 06:15:27)
- Location:
- user
- Files:
-
- 1 deleted
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
user/index.rst
rb5014fe rc4da705 43 43 rsb/index 44 44 45 support/index46 47 45 glossary/index 48 46 -
user/overview/index.rst
rb5014fe rc4da705 2 2 3 3 Introduction 4 ============ 4 ************ 5 5 6 6 Overview 7 -------- 7 ======== 8 8 9 9 You are someone looking for a real-time operating system. This document … … 18 18 19 19 Features 20 -------- 20 ======== 21 21 22 22 The Real-Time Executive for Multiprocessor Systems (:ref:term:`RTEMS`) is a … … 183 183 - Support to stay in synchronization with FreeBSD 184 184 185 Support 186 ======= 187 .. index:: Support 188 189 RTEMS offers a variety of support options. 190 191 This section covers all options available to both users and developers. If you 192 believe this is a bug report please submit it to the bug tracker otherwise the 193 developers mailing list is the default location to send the report. 194 195 RTEMS Project Support 196 --------------------- 197 .. index:: RTEMS Project Support 198 199 The following support channels are provided by the RTEMS Project and provide 200 direct access to the RTEMS community. 201 202 Bug Tracker 203 ~~~~~~~~~~~ 204 .. index:: Bugs 205 .. index:: Reporting bugs 206 207 The bug tracker can be found at the :r:url:`bugs`. 208 209 See the `Submission Guidelines <http://devel.rtems.org/wiki/NewTicket/>`_ for 210 details on submitting a ticket. 211 212 Be sure to do a cursory search for any tickets that may be relevant to your 213 problem. 214 215 If you are unsure about your issue status submit a ticket and we will help you 216 sort it out. 217 218 Documentation 219 ~~~~~~~~~~~~~ 220 221 The latest user documentation can always be found at the :r:url:`docs`. 222 223 .. _support-mailing-lists: 224 225 Mailing Lists 226 ~~~~~~~~~~~~~ 227 .. index:: Community 228 .. index:: Mailing lists 229 230 We have several mailing lists for RTEMS users and developers. 231 232 * :r:list:`announce` 233 * Announcements for major and other project-related issues. 234 235 * :r:list:`bugs` 236 * Bugs email from :r:url:`bugs`. 237 238 * :r:list:`devel` 239 * Developers list, this is for developers of RTEMS itself. 240 241 242 * :r:list:`build` 243 * Results from the testing and building of RTEMS. 244 245 * :r:list:`users` 246 * Users of RTEMS. 247 248 * :r:list:`vc` 249 * Commits to the RTEMS master repository. 250 251 252 IRC 253 ~~~ 254 .. index:: Community 255 .. index:: IRC 256 257 RTEMS IRC is available on the Freenode network. See the `Freenode 258 <http://www.freenode.net/>`_ web site for details on connecting, selecting a 259 nickname, and general usage tips. If you are new to IRC it is recommended 260 reading. 261 262 These are the current IRC channels. 263 264 **#rtems** 265 266 This is a general channel for all things RTEMS. You can just hang out with 267 other RTEMS users and developers to talk about RTEMS, using RTEMS or to make 268 contact with other RTEMS users. 269 270 The ``#rtems`` channel is logged. You can find the logs at 271 http://www.rtems.org/irclogs/. You can search the logs using Google by adding: 272 273 **site:rtems.org inurl:irclogs** 274 275 to your search terms. 276 277 Developers 278 ~~~~~~~~~~ 279 .. index:: Community 280 .. index:: Developers 281 282 Developers can find help and support on the mailing lists, see 283 :ref:`support-mailing-lists`. 284 285 Technical documents including design, :r:url:`gsoc`, :r:url:`socis` can be 286 found on the :r:url:`devel`. 287 288 Commercial Support Services 289 --------------------------- 290 291 The wider RTEMS community has developers and organizations who can provide 292 commercial support services. These services range from training, implementing 293 new features in RTEMS, deployment of RTEMS< helping establish a new project 294 environment for a team, to application and system design. 295 296 The RTEMS Project does not endorse or promote any provider of these services 297 and we recommend you use a search engine to locate a suitable provider. If you 298 are unsure please contact a provider and see what is available. 299 300 If you develop a new feature or you have someone do this for you we recommend 301 you have the work submitted to the project and merged. Once accepted into the 302 project the work will be maintained as part of the development process within 303 the project and this is a benefit for. 304 185 305 Real-time Application Systems 186 ----------------------------- 306 ============================= 187 307 188 308 Real-time application systems are a special class of computer applications. … … 219 339 220 340 Real-time Executive 221 ------------------- 341 =================== 222 342 223 343 Fortunately, real-time operating systems, or real-time executives, serve as a
Note: See TracChangeset
for help on using the changeset viewer.