Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-06-06 16:50:55 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Beginning to update comments to reflect new organization of the boards/ sub-directory.

Browse Source
This commit is contained in:
Gregory Nutt
2019-08-08 08:46:54 -06:00
parent 1e0987a729
commit 240926c995
29 changed files with 101 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files
include/nuttx/arch.h
+5 -5
View File
@@ -78,12 +78,12 @@
*
* 4. Board-Specific Interfaces.
*
* Any interface which is unique to a board should be prefixed with
* Any interface that is unique to a board should be prefixed with
* the board name, for example stm32f4discovery_. Sometimes the board
* name is too long so stm32_ would be okay too. These should be
* prototyped in boards/<board>/src/<board>.h and should not be used
* outside of that board directory since board-specific definitions
* have no meaning outside of the board directory.
* name is too long so stm32_ would be okay too. These should be
* prototyped in boards/<arch>/<chip><board>/src/<board>.h and should
* not be used outside of that board directory since board-specific
* definitions have no meaning outside of the board directory.
*/
/****************************************************************************
include/nuttx/board.h
+10 -10
View File
@@ -75,21 +75,21 @@
*
* Board related declarations are retained in this header file.
*
* There is also a boards/<board>/include/board.h header file that
* can be used to communicate other board-specific information between
* the architecture logic and even application logic. Any definitions
* which are common between a single architecture and several boards
* should go in this board.h header file; this file is reserved for
* board-related definitions common to all architectures.
* There is also a boards/<arch>/<chip>/<board>/include/board.h header
* file that can be used to communicate other board-specific information
* between the architecture logic and even application logic. Any
* definitions that are common between a single architecture and several
* boards should go in this board.h header file; this file is reserved
* for board-related definitions common to all architectures.
*
* 4. Board-Specific Interfaces.
*
* Any interface which is unique to a board should be prefixed with
* Any interface that is unique to a board should be prefixed with
* the board name, for example stm32f4discovery_. Sometimes the board
* name is too long so stm32_ would be okay too. These should be
* prototyped in boards/<board>/src/<board>.h and should not be used
* outside of that board directory since board-specific definitions
* have no meaning outside of the board directory.
* prototyped in boards/<arch>/<chip>/<board>/src/<board>.h and should
* not be used outside of that board directory since board-specific
* definitions have no meaning outside of the board directory.
*/
#ifndef __INCLUDE_NUTTX_BOARD_H
include/nuttx/spi/spi_bitbang.c
+1 -1
View File
@@ -1,5 +1,5 @@
/****************************************************************************
* boards/nuttx/spi/spi_bitbang.c
* include/nuttx/spi/spi_bitbang.c
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>