See
struct _rtems_filesystem_operations_table {
rtems_filesystem_mt_entry_lock_t lock_h;
rtems_filesystem_mt_entry_unlock_t unlock_h;
...
};
On 03/12/15 15:30, Martin Galvan wrote:
Oh, I see. Do you happen to remember where that lock is
acquired/released? I saw the up/down macros in the eCo
On 12/01/15 20:44, Pavel Pisa wrote:
Hello Chris,
On Monday 30 of November 2015 22:52:28 Chris Johns wrote:
On 30/11/2015 10:16 AM, Pavel Pisa wrote:
I have applied your patches on RSB master the result
is identical to the last one with updated libPNG.
I have rerun build and all packages has
On 12/04/15 01:30, Martin Galvan wrote:
Oh, I see. Do you happen to remember where that lock is
acquired/released?
Have a look here ...
https://git.rtems.org/rtems/tree/cpukit/libfs/src/jffs2/src/fs-rtems.c#n318
Chris
___
devel mailing list
devel@rt
The ISR will send a transient event to the task specified in bus->taskid.
Make sure that the correct task_id is written to this field before waiting
for the transient event to arrive.
Fixes #2483
---
c/src/lib/libbsp/arm/raspberrypi/i2c/i2c.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/c/
Oh, I see. Do you happen to remember where that lock is
acquired/released? I saw the up/down macros in the eCos code at the
points where the RTEMS mutex_lock/unlock would be called (e.g. in
jffs2_new_inode). up/down end up calling Cyg_Mutex::unlock/lock, which
aren't empty, so it seems that there's
