Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/sys/dev/putter/putter_sys.h

69 lines
2.6 KiB
C
Raw Normal View History

Allow to register configuration routines to putter. Once a configuration routine has been attached to the putter device minor number, the configuration routine will be called when the device is opened. This is required for subsystems which enter the kernel only through the file descriptor and cannot configure themselves via another route (like puffs does via the mount() syscall). Keep the minor number 0 for "wildcard" uses where we do not require a hardwired config routine (e.g. the puffs case).
2007-11-20 21:35:22 +03:00
/* $NetBSD: putter_sys.h,v 1.3 2007/11/20 18:35:22 pooka Exp $ */
Part 2/n of extensive changes to request transport to/from userspace: Rip the transport code completely out of puffs and generalize it into an independent module which will be used for multiple purposes in the future. This module is called the Pass-to-Userspace Transporter (known as "putter" among friends). This is very much work-in-progress and one dependency with puffs remains: the request framing format. The device name is still /dev/puffs, but that will change soon. Users of puffs need the following in their kernel configs now: pseudo-device putter
2007-11-11 00:45:04 +03:00
/*
* Copyright (c) 2007 Antti Kantee. All Rights Reserved.
*
* Development of this software was supported by the
* Research Foundation of Helsinki University of Technology
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
* OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
* SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*/
* split the putter header into a kernel version and a userland version + install latter to /usr/include/dev/putter * remove last dependencies to puffs from putter, it's completely independent now
2007-11-12 19:39:32 +03:00
#ifndef _DEV_PUTTER_PUTTERSYS_H_
#define _DEV_PUTTER_PUTTERSYS_H_
Part 2/n of extensive changes to request transport to/from userspace: Rip the transport code completely out of puffs and generalize it into an independent module which will be used for multiple purposes in the future. This module is called the Pass-to-Userspace Transporter (known as "putter" among friends). This is very much work-in-progress and one dependency with puffs remains: the request framing format. The device name is still /dev/puffs, but that will change soon. Users of puffs need the following in their kernel configs now: pseudo-device putter
2007-11-11 00:45:04 +03:00
#include <sys/param.h>
* split the putter header into a kernel version and a userland version + install latter to /usr/include/dev/putter * remove last dependencies to puffs from putter, it's completely independent now
2007-11-12 19:39:32 +03:00
#include <sys/proc.h>
#include <dev/putter/putter.h>
Part 2/n of extensive changes to request transport to/from userspace: Rip the transport code completely out of puffs and generalize it into an independent module which will be used for multiple purposes in the future. This module is called the Pass-to-Userspace Transporter (known as "putter" among friends). This is very much work-in-progress and one dependency with puffs remains: the request framing format. The device name is still /dev/puffs, but that will change soon. Users of puffs need the following in their kernel configs now: pseudo-device putter
2007-11-11 00:45:04 +03:00
Allow to register configuration routines to putter. Once a configuration routine has been attached to the putter device minor number, the configuration routine will be called when the device is opened. This is required for subsystems which enter the kernel only through the file descriptor and cannot configure themselves via another route (like puffs does via the mount() syscall). Keep the minor number 0 for "wildcard" uses where we do not require a hardwired config routine (e.g. the puffs case).
2007-11-20 21:35:22 +03:00
/*
* Configuration data.
*
* Users of putter currently must be registered statically. This sucks,
* I know, but what are you going to do since you need static allocation
* for /dev nodes anyway. Ok, we could be slightly more forgiving about
* this, but let's just wait for devfs for now.
*/
#define PUTTER_MINOR_WILDCARD 0
#define PUTTER_MINOR_PUD 1
#define PUTTER_MINOR_COMPAT 0x7ffff /* will die sometime soon */
Part 2/n of extensive changes to request transport to/from userspace: Rip the transport code completely out of puffs and generalize it into an independent module which will be used for multiple purposes in the future. This module is called the Pass-to-Userspace Transporter (known as "putter" among friends). This is very much work-in-progress and one dependency with puffs remains: the request framing format. The device name is still /dev/puffs, but that will change soon. Users of puffs need the following in their kernel configs now: pseudo-device putter
2007-11-11 00:45:04 +03:00
struct putter_ops {
int (*pop_getout)(void *, size_t, int, uint8_t **,size_t *,void **);
void (*pop_releaseout)(void *, void *, int);
size_t (*pop_waitcount)(void *);
Bounds-check responses from userspace.
2007-11-12 20:42:13 +03:00
int (*pop_dispatch)(void *, struct putter_hdr *);
Part 2/n of extensive changes to request transport to/from userspace: Rip the transport code completely out of puffs and generalize it into an independent module which will be used for multiple purposes in the future. This module is called the Pass-to-Userspace Transporter (known as "putter" among friends). This is very much work-in-progress and one dependency with puffs remains: the request framing format. The device name is still /dev/puffs, but that will change soon. Users of puffs need the following in their kernel configs now: pseudo-device putter
2007-11-11 00:45:04 +03:00
int (*pop_close)(void *);
};
Allow to register configuration routines to putter. Once a configuration routine has been attached to the putter device minor number, the configuration routine will be called when the device is opened. This is required for subsystems which enter the kernel only through the file descriptor and cannot configure themselves via another route (like puffs does via the mount() syscall). Keep the minor number 0 for "wildcard" uses where we do not require a hardwired config routine (e.g. the puffs case).
2007-11-20 21:35:22 +03:00
typedef int (*putter_config_fn)(int, int, int);
Part 2/n of extensive changes to request transport to/from userspace: Rip the transport code completely out of puffs and generalize it into an independent module which will be used for multiple purposes in the future. This module is called the Pass-to-Userspace Transporter (known as "putter" among friends). This is very much work-in-progress and one dependency with puffs remains: the request framing format. The device name is still /dev/puffs, but that will change soon. Users of puffs need the following in their kernel configs now: pseudo-device putter
2007-11-11 00:45:04 +03:00
struct putter_instance;
struct putter_instance *putter_attach(pid_t, int, void *,
struct putter_ops *);
void putter_detach(struct putter_instance *);
void putter_notify(struct putter_instance *);
Allow to register configuration routines to putter. Once a configuration routine has been attached to the putter device minor number, the configuration routine will be called when the device is opened. This is required for subsystems which enter the kernel only through the file descriptor and cannot configure themselves via another route (like puffs does via the mount() syscall). Keep the minor number 0 for "wildcard" uses where we do not require a hardwired config routine (e.g. the puffs case).
2007-11-20 21:35:22 +03:00
int putter_register(putter_config_fn, int);
Part 2/n of extensive changes to request transport to/from userspace: Rip the transport code completely out of puffs and generalize it into an independent module which will be used for multiple purposes in the future. This module is called the Pass-to-Userspace Transporter (known as "putter" among friends). This is very much work-in-progress and one dependency with puffs remains: the request framing format. The device name is still /dev/puffs, but that will change soon. Users of puffs need the following in their kernel configs now: pseudo-device putter
2007-11-11 00:45:04 +03:00
* split the putter header into a kernel version and a userland version + install latter to /usr/include/dev/putter * remove last dependencies to puffs from putter, it's completely independent now
2007-11-12 19:39:32 +03:00
#endif /* _DEV_PUTTER_PUTTERSYS_H_ */