From owner-freebsd-mobile@FreeBSD.ORG Thu May 1 08:56:28 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C45B37B401 for ; Thu, 1 May 2003 08:56:28 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5D3843FA3 for ; Thu, 1 May 2003 08:56:24 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h41FuNA7008091; Thu, 1 May 2003 09:56:24 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 01 May 2003 09:56:17 -0600 (MDT) Message-Id: <20030501.095617.72710939.imp@bsdimp.com> To: cbiffle@safety.net, mobile@freebsd.org From: "M. Warner Losh" In-Reply-To: <200305010115.05326.cbiffle@safety.net> References: <200305010115.05326.cbiffle@safety.net> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: devctl for non-devd userland processes X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 15:56:28 -0000 In message: <200305010115.05326.cbiffle@safety.net> "Cliff L. Biffle" writes: : Good ${time_of_day}! : : I'm hacking on KDE's laptop hardware monitoring support (ACPI, battery, : hardware detection, etc.). I'd like to be able to provide device : notification -- for example, notifying the user when a PCMCIA device is : recognized and what device it's been bound to. In my mind, the logical way : to do this is devctl -- it's a generic interface and an elegant mechanism. : However, devd is already sucking on devctl. Correct. : Do you have any existing plans for providing a mechanism for non-devd : processes to play nice with devd, in terms of devctl? The sorts of options : that pop into my head are a userland socket/pipe interface to devd, or even : cloning for devctl (though that strikes me as excessive, perhaps). Device cloning was what I had in mind. I really don't want to deal with multiple userland processes just to have devd run. : If you don't have any plans along these lines, I'll either work : around it for now or work out an interface and toss patches into the : fray. I'm most partial to a cloning device, but I might be talked into something else. : Perhaps more importantly, is there a dev community for devd/devctl, : so I might stop pestering you personally? :-) mobile@ might be a good place. Warner