9
0
Fork 0
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@1862 7fd9a85b-ad96-42d3-883c-3090e2eb8679
This commit is contained in:
patacongo 2009-06-08 14:18:41 +00:00
parent d73e96f699
commit ffd539863e
4 changed files with 23 additions and 13 deletions

View File

@ -763,5 +763,9 @@
* arch/arm/str71x/str71x_serial.c: The STR711 interrupt driven serial driver
finally works after some extradinary measures to handle missed interrupts.
NSH is fully functional on the Olimex STR-P711 board.
* example/nsh: Moved architecture specific files from NSH directory to board-
specific directories.
* config/olimex-strp711/src/up_nsh.c: Add an NSH board specific directory for
for the Olimex STR7P11 board.

View File

@ -8,7 +8,7 @@
<tr align="center" bgcolor="#e4e4e4">
<td>
<h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
<p>Last Updated: June 07, 2009</p>
<p>Last Updated: June 08, 2009</p>
</td>
</tr>
</table>
@ -1432,6 +1432,10 @@ nuttx-0.4.8 2009-xx-xx Gregory Nutt &lt;spudmonkey@racsa.co.cr&gt;
* arch/arm/str71x/str71x_serial.c: The STR711 interrupt driven serial driver
finally works after some extradinary measures to handle missed interrupts.
NSH is fully functional on the Olimex STR-P711 board.
* example/nsh: Moved architecture specific files from NSH directory to board-
specific directories.
* config/olimex-strp711/src/up_nsh.c: Add an NSH board specific directory for
for the Olimex STR7P11 board.
pascal-0.1.3 2009-xx-xx Gregory Nutt &lt;spudmonkey@racsa.co.cr&gt;

View File

@ -1262,7 +1262,7 @@ static int lm3s_txavail(struct uip_driver_s *dev)
****************************************************************************/
/****************************************************************************
* Function: lm3s_initialize
* Function: lm3s_ethinitialize
*
* Description:
* Initialize the Ethernet driver for one interface
@ -1278,9 +1278,9 @@ static int lm3s_txavail(struct uip_driver_s *dev)
****************************************************************************/
#if LM3S_NETHCONTROLLERS > 1
int lm3s_initialize(int intf)
int lm3s_ethinitialize(int intf)
#else
static inline int lm3s_initialize(int intf)
static inline int lm3s_ethinitialize(int intf)
#endif
{
struct lm3s_driver_s *priv = &g_lm3sdev[intf];
@ -1366,7 +1366,7 @@ static inline int lm3s_initialize(int intf)
#if LM3S_NETHCONTROLLERS == 1
void up_netinitialize(void)
{
(void)lm3s_initialize(0);
(void)lm3s_ethinitialize(0);
}
#endif

View File

@ -300,7 +300,7 @@ EXTERN int lm3s_dumpgpio(uint32 pinset, const char *msg);
EXTERN int weak_function gpio_irqinitialize(void);
/****************************************************************************
* Function: lm3s_initialize
* Function: lm3s_ethinitialize
*
* Description:
* Initialize the Ethernet driver for one interface. If the LM3S chip
@ -319,22 +319,24 @@ EXTERN int weak_function gpio_irqinitialize(void);
****************************************************************************/
#if LM3S_NETHCONTROLLERS > 1
EXTERN int lm3s_initialize(int intf);
EXTERN int lm3s_ethinitialize(int intf);
#endif
/****************************************************************************
* The external functions, lm3s_spiselect and lm3s_spistatus must be provided
* by board-specific logic. The are implementations of the select and status
* methods SPI interface defined by struct spi_ops_s (see include/nuttx/spi.h).
* All othermethods (including up_spiinitialize()) are provided by common
* All other methods (including up_spiinitialize()) are provided by common
* logic. To use this common SPI logic on your board:
*
* 1. Provide lm3s_spiselect() and lm3s_spistatus() functions in your
* board-specific logic. This function will perform chip selection and
* 1. Provide logic in lm3s_boardinitialize() to configure SPI chip select
* pins.
* 2. Provide lm3s_spiselect() and lm3s_spistatus() functions in your
* board-specific logic. These functions will perform chip selection and
* status operations using GPIOs in the way your board is configured.
* 2. Add a call to up_spiinitialize() in your low level initialization
* logic
* 3. The handle returned by up_spiinitialize() may then be used to bind the
* 3. Add a call to up_spiinitialize() in your low level application
* initialization logic
* 4. The handle returned by up_spiinitialize() may then be used to bind the
* SPI driver to higher level logic (e.g., calling
* mmcsd_spislotinitialize(), for example, will bind the SPI driver to
* the SPI MMC/SD driver).