CVS log for emstar/fusd/include/fusd_msg.h
	Help

Request diff between arbitrary revisions / Display revisions graphically / Jump to LXR

Big commit -- the bulk of the Cygwin compatibility is being checked in here.
The Cygwin port doesn't really run yet since FUSD hasn't been ported, but,
with this checkin, the rest of the repository compiles.

fix for 2.6

* inc version number to force fusd upgrade
* added helpful error messages

more patches to work with kernel 2.6.

* minor changes to support new refcounting in kfusd.
* changes to support 32-bit device numbers.. though userspace is still
  in 16 bit-land

* major checkin of fusdnet work.

* fusd API changes
  * fusd_context_t instead of g_event_t
  * added option to disable fusdnet functionality
  * propagated changes throughout libdev etc
  * changes to fusd_msg to support new fusdnet message type

* audio server
  * got rid of stupid rflink junk
  * fixed fusd api change

fusdd_client -
Creates its client files in /dev/net/<ip_addr>/<dev_name>
Now actually returns data that it gets from the server back
to the requesting client - tested with echocat and my simple
tcp_server.

Does NOT send poll_diffs or read_requests to the server yet -
this will be a simple addition once lew and i coordinate.

fusdd_client has basic functionality working -
creates connection, sends data to remote host,
when it gets data back can match it u with a client's request,
and tries to send the data back to the client. (This last part
is not verified yet).

more checkins for proto-fusdnet

backed out changes related to fusdnet

Took out segment in command_dev_open that kills a command-device if
a usage call-back is instantiated, but returns a NULL pointer.

Added code to fusdd_client.c - in order to create a :
dev/fusd/net device which accepts commands to connect to remote hosts.
Once it creates a socket and connection, it creates a new packet-device
(the name is provided in the connection call to the cmd-device)
which accepts commands to the host and will automatically send whatever
is written to the packet-device to the remote host.

Added code to emtos to translate dbg commands in TinyOS to elog commands.

started form on fusdnet (tm)

* Modified FUSD to support unlimited numbers of devices in non-devfs mode
* Modified FUSD status protocol to support diffs with a 10-second refresh

FUSD no longer depends on DevFS!!!

TO use this feature, compile on a system with a non-devfs kernel,
insert the module, and run the fusdd user daemon.  Otherwise it
works identically to devfs fusd.

This also involves a change to the fusd status output, so old fusd's
are not compatible with the new fusd.

added the copyright notice to all the source code in the cens repository

- added a copyright notice to all the source code files in the cens
repository

Changed the FUSD status ticker over to integrate text and binary into
a single device file.  The user simply performs an ioctl() on /dev/status
after opening it (and before reading it) to switch into binary mode.

Maybe userspace tickers can use this scheme eventually...

New restriction: must use linux kernel v2.4.10 or later, since my
2.4.9's devfs_register doesn't properly create subdirectories, and
for now it's easier to force 2.4.10 or later than to handhold the earlier
devfs implementations into creating a directory structure.

Implemented a "binary status" ticker, giving a C-struct version of the
FUSD status information, to avoid having to put parsing code into clients
such as emrun.

Factored out the code that exponentially grows the fusd status buffer,
so it can be shared by both the binary and text versions of build_status.

Renamed fusd_status_t to fusd_statcontext_t, since I wanted to use the
fusd_status_t name for the structure used to communicate status between
the kernel module and userspace.

Moved /dev/fusd and /dev/fusd_status into a /dev/fusd directory; renamed
/dev/fusd/control and /dev/fusd/status.

/dev/fusd/* now have constants instead of literals in the code.

Changed registration max name length from 31 to 47

some initial restructuring of message structs

Merged FUSD with main branch again

FUSD change: fusd_get_polldiff_current_flags -> fusd_get_polldiff_cached_state

I've changed the name of the above function to
"fusd_get_polldiff_cached_state", which I think more accurately describes
what it actually does.  (I realized that the name was potentially confusing
while trying to write an explanation of how the poll_diff function works.)
The "current state" (according to the explanation I'm writing up), is the
actual poll state known by the driver at any given instant.  The argument
passed in a poll_diff callback, on the other hand, is not really the
"current" state, but rather the state that the kernel has *cached*.  Given
the two terms "current" and "cached", it's easier to explain that you
should "update the cache if the cache doesn't match the current value".

Merged in the new FUSD from the main development branch

Major changes!!!!!

Restartable system calls have been implemented but this unfortunately
required quite a few changes to the guts of FUSD, which has not been
battle tested yet.  It passes my test suites but this thing needs to be
banged on for a while longer before I'll feel safe with it.

Some highlights of changes:
 -- restartable syscalls implemented
 -- fusd_fops_call() was split into a top half (that generates a message)
    and a bottom half (that waits for the reply).  This makes restartable
    syscalls much easier.
 -- fusd_fops_call_send() -- the top half as described above -- is now
    further decomposed into a function called dev_send_msg which puts a
    message on a device's outgoing message queue.  Used by fusd_fops_reply
    to easily forge a "close" request in response to a successful open
    request that has no connection.
 -- "hints" (i.e. the quick index hint into the fusd_dev's reply array)
    is now part of the fusd_msg instead of being kept internally.  This
    makes the handling of all that state much more scalable since it's
    kept with the request - why didn't I think of this earlier!?!??

Lots of other minor (and some not so minor) things - see diffs for details

Small change to show more forcefully that FUSD_FOPS_REPLY must be 1
greater than FUSD_FOPS_CALL, etc.

kernel now passes UID and GID to drivers for their examining pleasure

major overhaul of internals: outgoing messages are now part of DEVICE state, not FILE state

fixes to make in-kernel compilation easier

changed sense of FUSD_NOREPLY

this either completely fucked everything up or implemented select

new notify structure..
poll_diff() implemented

changed notify to selected
added callback dispatch for selected and unblock
added accessor inline functions

implemented ioctl for clients

maybe read works now, god willing

*** empty log message ***

*** empty log message ***

*** empty log message ***

*** empty log message ***

first version of all files