From owner-freebsd-current@FreeBSD.ORG Fri Oct 15 14:36:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A7B416A4CF for ; Fri, 15 Oct 2004 14:36:21 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E61A43D48 for ; Fri, 15 Oct 2004 14:36:20 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([138.89.97.54]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041015143619.FIRG23519.out001.verizon.net@[10.0.3.231]>; Fri, 15 Oct 2004 09:36:19 -0500 From: "Alexandre \"Sunny\" Kovalenko" To: cswiger@mac.com In-Reply-To: <416EDA36.1070403@DeepCore.dk> References: <20041013205141.GA874@galgenberg.net> <20041014105927.GU718@empiric.icir.org><416EC5F4.8000203@mac.com> <416EDA36.1070403@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1097850967.843.14.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 15 Oct 2004 10:36:08 -0400 Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [138.89.97.54] at Fri, 15 Oct 2004 09:36:18 -0500 cc: freebsd-current@freebsd.org Subject: Re: atapicam(4) as KLD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 14:36:21 -0000 On Thu, 2004-10-14 at 15:57, Søren Schmidt wrote: > Chuck Swiger wrote: > > Michael Nottebrock wrote: > > > >> On Thursday 14 October 2004 12:59, Bruce M Simpson wrote: > >> > >>> On Wed, Oct 13, 2004 at 10:51:41PM +0200, Ulrich Spoerlein wrote: > >>> [ ...well made userland point snipped... ] > >>> Unfortunately, due to the way ata and atapicam are implemented right > >>> now, > >>> this is unlikely to happen soon. > >> > >> > >> Easy workaround: Put atapicam into GENERIC. I'm waiting for that to > >> happen ever since atapicam entered the tree. > > > > > > I'd strongly agree, unless there is a major downside to doing so. > > > > (Disclaimer: Having ATAPICAM in GENERIC would reduce my email support > > burden for the dvd+rw-tools port by a noticable fraction. :-) > > But will do the opposite to my mailbox, and I *dont* support atapicam, > so I think its a bad idea, besides I waste enough time as is, thanks... > Since I was one of the people responsible for using up space in Søren's mailbox in the past, I felt obliged to chime in -- my laptop (AVERATEC 3150H) was complaining about ad0 and would eventually hang if it had 'device atapicam'. I have disabled it and lived happily thereafter. To be fair, I do not know if it still is the case. If there is enough interest out there, I can plug it back in. However, I think this would be something to consider before making it part of GENERIC kernel. FWIW. --- Alexandre "Sunny" Kovalenko.