From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 12 19:37:23 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 158E516A4CE for ; Sat, 12 Jun 2004 19:37:23 +0000 (GMT) Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC1CE43D48 for ; Sat, 12 Jun 2004 19:37:22 +0000 (GMT) (envelope-from eaja@erols.com) X-Info: This message was accepted for relay by smtp03.mrf.mail.rcn.net as the sender used SMTP authentication X-Trace: qkTgJtUnPhpCFTQUhEYqABuhfeN4cGqzRZODxxVNhHE= Received: from 165.sub-166-141-30.myvzw.com ([166.141.30.165] helo=localhost) by smtp03.mrf.mail.rcn.net with asmtp (Exim 3.35 #7) id 1BZEJ6-0002b9-00 for freebsd-hackers@freebsd.org; Sat, 12 Jun 2004 15:36:52 -0400 Date: Sat, 12 Jun 2004 15:36:33 -0400 From: Eric Jacobs To: freebsd-hackers@freebsd.org Message-Id: <20040612153633.315938cf.eaja@erols.com> In-Reply-To: <20040612184617.65b746f4.sebastian.ssmoller@gmx.net> References: <20040612184617.65b746f4.sebastian.ssmoller@gmx.net> X-Mailer: Sylpheed version 0.8.5 (GTK+ 1.2.10; i386-portbld-freebsd4.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: lpt module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jun 2004 19:37:23 -0000 On Sat, 12 Jun 2004 18:46:17 +0200 sebastian ssmoller wrote: > > so i decided to play around a bit with the lpt module. first thing i > noticed when compiled lpt as module is: i cannot unload it (kldunload > says: device not configured). somewhere in the net i read that this is > an expected behaviour (as it is for usb afaik) because lpt module does > not release memory properly (?) The lpt driver needs a device_detach method in sys/ppbus/lpt.c. Might want to look at sio_detach in sio for hints. It will need to ensure that the device is closed, release bus resources, and destroy its cdevs, and possibly some other non-obvious things (haven't looked closely)