user space mmap / kcomedilib consistency

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Dave,

At some point in the semi-near future I'd like to make the behaviour of 
mmap'ing from user space, and kcomedilib consistent, so I'd like some input 
on what the preferred behaviour/function names should be.  In summary, we 
have:

In kcomedilib:

comedi_set_user_int_count() - which you pass the total number of bytes you 
have read from comedi's buffer. 

comedi_get_buf_head_pos() - which returns the total number of bytes the 
driver has written to comedi's buffer.

In user-space:

comedi_get_buffer_contents() - which returns the number of unread bytes 
currently available in comedi's buffer

comedi_mark_buffer_read() - which increments comedi's count of how many bytes 
you have read out of the buffer

And also, there is

comedi_get_buffer_offset() - which returns the number of bytes offset the 
next unread byte is from the beginning of the buffer (not necessary since the 
user can keep track of this himself).

I don't have any strong preferences, except that the name of 
comedi_set_user_int_count() is outdated.  Also, as a side note there really 
isn't any support for output currently.  Oh, and would changing the names of 
some of the members of the comedi_bufinfo_struct cause binary 
incompatibilities (not changing their usage, just their names, like 
buf_user_count to buf_read_count)?

- -- 
Frank

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+VDIf5vihyNWuA4URAgIgAJ9ynwtGYiwzOkhdag8SUB+7JzBxoACfUu4q
n8UbZiEiUKEPpoPdxoqG7WA=
=lpnc
-----END PGP SIGNATURE-----

Received on 2003-02-20Z01:40:47