misc updates

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@1869 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2009-06-10 12:27:44 +00:00
parent 64497e92d2
commit c678c8db00
2 changed files with 10 additions and 4 deletions

View File

@ -157,9 +157,14 @@
/* Endpoint register mask (no toggle fields) */
#define USB_EPR_MASK (USB_EPR_CTRRX|USB_EPR_SETUP|USB_EPR_TFIELD|\
#define USB_EPR_NOTOGGLE_MASK (USB_EPR_CTRRX|USB_EPR_SETUP|USB_EPR_TFIELD|\
USB_EPR_KIND|USB_EPR_CTRTX|USB_EPR_ADDRFIELD)
/* Toggles only */
#define USB_EPR_TXDTOG_MASK (USB_EPR_TXSTAT_MASK|USB_EPR_NOTOGGLE_MASK)
#define USB_EPR_RXDTOG_MASK (USB_EPR_RXSTAT_MASK|USB_EPR_NOTOGGLE_MASK)
/************************************************************************************
* Public Types
************************************************************************************/

View File

@ -40,7 +40,7 @@ GNU Toolchain Options
NOTE: the CodeSourcery and devkitARM toolchains are Windows native toolchains.
The NuttX buildroot toolchain is a Cygwin toolchain. There are several limitations
to using a Windows based toolchain in a Cygwin environment. The two biggestg are:
to using a Windows based toolchain in a Cygwin environment. The two biggest are:
1. The Windows toolchain cannot follow Cygwin paths. Path conversions are
performed automatically in the Cygwin makefiles using the 'cygpath' utility
@ -54,11 +54,11 @@ GNU Toolchain Options
That is because you are building the copy of the file in the "fake" symbolic
directory. If you use a Windows toolchain, you should get in the habit of
making like this:
make clean_context; make CROSSDEV=arm-none-eabi-
An alias in your .bashrc file might make that less painful.
NuttX buildroot Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^
@ -68,6 +68,7 @@ NuttX buildroot Toolchain
If you have no Cortex-M3 toolchain, one can be downloaded from the NuttX
SourceForge download site (https://sourceforge.net/project/showfiles.php?group_id=189573).
This GNU toolchain builds and executes in the Cygwin environment.
1. You must have already configured Nuttx in <some-dir>/nuttx.