From: Jamie Faris <farisj@gm...> - 2006-12-03 18:50:41
First off, thanks for the great work on rioutil. I've been using it for a
couple years now with my Rio Fuse and it's met my needs well.
I've been putting together an Amarok plugin to handle Rio devices and I've got
a few questions.
The rio.h file has a declaration for first_free_file_rio(), but I can't find
an implementation anywhere. This is what I've been using and that's worked
for me but it seems like it might be different for other Rios?
int first_free_file_rio (rios_t *rio, u_int8_t memory_unit)
return ((flist_first_free_rio(rio, memory_unit) >> 4) - 1);
When deleting a file, the num and inum fields would get out of sync, leading
to deleting the wrong file on subsequent deletes. A small change to
flist_remove_rio fixed that: adding num-- where it does inum-- for each file.
diff -r1.10 file_list.c
What is the difference between the num and inum fields? As far as I can see
they always hold the same value.
I came across a problem where the device would remain locked after a delete
failed. The function would return without unlocking the device. A quick
look through the code found a few more places where that could happen, so I
just replaced 'return' with the UNLOCK macro.
This diff also replaces sys/syslimits.h with limits.h which makes it compile
on my Debian system and seems to be a more correct way of doing it, but I
really couldn't find a definitive answer through google.
retrieving revision 1.23
diff -r1.23 song_management.c
< #include <sys/syslimits.h>
> #include <limits.h>
< #if !defined(PATH_MAX)
< #define PATH_MAX 1024
< return -1;
< return -1;
< return ret;
How does aborting a transfer work? I see the abort field in the rios struct.
Will simply setting that to 1 abort the transfer at the next opportunity?
Is there a way to ask the Rio device what filetypes it supports?
Do you have plans for a new release soon?
Sorry for the long mail. I hope it all makes sense - let me know if you need
any more info. Again, thanks for the great library!