From owner-freebsd-hackers Wed Mar 21 15: 7:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C413F37B722 for ; Wed, 21 Mar 2001 15:07:16 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LN4lh03035; Wed, 21 Mar 2001 15:04:47 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212304.f2LN4lh03035@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Dokuchaev Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-reply-to: Your message of "Thu, 22 Mar 2001 04:57:24 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Mar 2001 15:04:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Did I say I'm doing it from userspace?! If I did (too lazy to dig into > > > sent-mail), I beg your pardon :) > > > > Your FreeBSD sample involved making an ioctl call, so it must have been > > from userspace. > > Is anything wrong with using ioctl calls from device driver? Perhaps a more polite answer is called for. 8) Ioctls allow user processes to make function calls within a device driver; they are a mechanism for exporting functionality from a device driver out into userspace. You don't call them from other device drivers, no. There are exported interfaces inside the kernel for doing this, and you will understand everything much better if you go look at a simple FreeBSD PCI device driver, particularly the _probe and _attach functions. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message