Cosmetic update to a few comments
This commit is contained in:
parent
58c05f365e
commit
011ff49685
|
@ -92,7 +92,8 @@ longjmp(). This context switching is available for 32-bit and 64-bit
|
|||
targets. You must, however, set the correct target in the configuration
|
||||
before you build: HOST_X86_64 or HOST_X86 for 62- and 32-bit targets,
|
||||
respectively. On a 64-bit machine, you can also force the 32-bit build
|
||||
with CONFIG_SIM_M32=y.
|
||||
with CONFIG_SIM_M32=y (which does not seem to be supported by more
|
||||
contemporary x86_64 compilers).
|
||||
|
||||
There are other 64-bit issues as well. For example, addresses are retained in
|
||||
32-bit unsigned integer types in a few places. On a 64-bit machine, the 32-bit
|
||||
|
|
|
@ -429,7 +429,7 @@ int local_release_halfduplex(FAR struct local_conn_s *conn)
|
|||
* to destory the FIFO will leave the FIFO resources in place after the
|
||||
* communications have completed.
|
||||
*
|
||||
* I am thinking that ther should be something like a timer. The timer
|
||||
* I am thinking that there should be something like a timer. The timer
|
||||
* would be started at the completion of each transfer and cancelled at
|
||||
* the beginning of each transfer. If the timer expires, then the FIFO
|
||||
* would be destroyed.
|
||||
|
|
Loading…
Reference in New Issue