From owner-freebsd-hackers Sat Dec 8 1: 5:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 9398437B416 for ; Sat, 8 Dec 2001 01:05:52 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fB894Ij46360; Sat, 8 Dec 2001 10:04:18 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dave Rufino Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: statefulness in character device drivers In-Reply-To: Your message of "Sat, 08 Dec 2001 09:02:08 GMT." Date: Sat, 08 Dec 2001 10:04:18 +0100 Message-ID: <46358.1007802258@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Dave R ufino writes: >> Most likely he means a per-open(2) opaque datum that is kept in >> struct file and passed to the underlying routines. > >Sorry, unbelievably bad at explaining myself. Per-open data is what i >meant. The reason I'm interested is it would make a full nvidia driver >port quite a bit easier. Sorry, I know of no current plans which adress this. The issue is non-trivial to fix because we currently don't pass dup(2) events through the vnode layer. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message