| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Update #3132.
|
|
|
|
| |
Update #3132.
|
|
|
|
| |
Update #3132.
|
|
|
|
| |
Update #3132.
|
|
|
|
| |
Update #3132.
|
|
|
|
| |
Close #3134.
|
|
|
|
|
|
| |
The top-level IO library structures should contain no special-case data.
Update #2859.
|
|
|
|
|
|
|
|
|
|
|
| |
Added a mmap file handler to struct _rtems_filesystem_file_handlers_r.
Updated each file handler object to support the default mmap handler.
Updated mmap() to call the mmap handler for MAP_SHARED.
Added a mmap file handler for shm
Added support for MAP_ANON in mmap().
Updates #2859
|
|
|
|
| |
Update #2833.
|
|
|
|
| |
Update #2859.
|
|
|
|
| |
Update #2408.
|
| |
|
|
|
|
| |
Update #2408.
|
| |
|
| |
|
|
|
|
| |
Use the fstat handler instead.
|
| |
|
|
|
|
|
|
|
|
|
| |
The readv() and writev() support was implemented in terms of multiple
calls to the read and write handlers. This imposes a problem on device
files which use an IO vector as single request entity. For example a
low-level network device (e.g. BPF(4)) may use an IO vector to create
one frame from multiple protocol layers each with its own IO vector
entry.
|
| |
|
| |
|
|
|
|
|
|
| |
This handler is necessary to implement the KQUEUE(2) system calls.
Add <sys/event.h> from FreeBSD 8.4.
|
|
|
|
|
|
|
| |
This handler is necessary to implement the SELECT(2) and POLL(2) system
calls.
Add <sys/poll.h> from FreeBSD 8.4.
|
|
|
|
| |
This is in line with Linux and FreeBSD.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add and use rtems_libio_exit_helper. Add rtems_libio_exit().
The fclose(stdin) etc. makes no sense during exit. This would use the
_REENT structure of the thread calling _exit().
|
|
|
|
|
| |
Rename open_dev_console() to rtems_libio_post_driver(). Rename
rtems_libio_supp_helper to rtems_libio_post_driver_helper.
|
|
|
|
|
| |
Add and use rtems_libio_helper function type. Add and use
rtems_libio_helper_null() instead of NULL pointer.
|
|
|
|
|
| |
This is the result of a sed script which converts all uses
of @{ into a consistent form.
|
| |
|
|
|
|
| |
http://www.google-melange.com/gci/task/view/google/gci2012/7996208
|
| |
|
| |
|
| |
|
|
|
|
| |
http://www.google-melange.com/gci/task/view/google/gci2012/7975223
|
| |
|
|
|
|
| |
http://www.google-melange.com/gci/task/view/google/gci2012/7992210
|
| |
|
| |
|
|
|
|
|
|
| |
The pathconf_limits_and_options field of
rtems_filesystem_mount_table_entry_t is now a const pointer to reduce
the read-write memory demands of file system instances.
|
|
|
|
|
|
|
|
|
|
|
| |
The scope of the file system operations is the file system instance.
The scope of the file system node handlers is the file location. The
benefit of moving the operations to the mount table entry is a size
reduction of the file location (rtems_filesystem_location_info_t). The
code size is slightly increased due to additional load instructions.
Restructure rtems_filesystem_mount_table_entry_t to improve cache
efficiency.
|
| |
|
|
|
|
|
|
|
| |
It is now the responsibility of the read() and write() handler to update
the offset field of the IO descriptor (rtems_libio_t). This change
makes it possible to protect the IO descriptor from concurrent access by
per file locks.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Script does what is expected and tries to do it as
smartly as possible.
+ remove occurrences of two blank comment lines
next to each other after Id string line removed.
+ remove entire comment blocks which only exited to
contain CVS Ids
+ If the processing left a blank line at the top of
a file, it was removed.
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to POSIX the lseek() function shall not, by itself, extend the
size of a file.
Remove the size field of rtems_libio_t. A file has only one size but
may have multiple open file descriptors. Thus a file size field in the
file descriptor may lead to inconsistencies.
New default handlers rtems_filesystem_default_lseek_file() and
rtems_filesystem_default_lseek_directory().
|
|
|
|
|
|
|
|
|
| |
The per file descriptor semaphore (field of rtems_libio_t) is unused in
RTEMS. There is a considerable memory overhead due to that. A
semaphore needs roughly 124 bytes which is huge compared to the
approximately 72 bytes for the file descriptor structure itself. Device
drivers can create their own synchronization primitives in the open
handler on demand.
|