From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH] libata: add ATAPI module option Date: Fri, 21 Oct 2005 23:34:56 -0400 Message-ID: <4359B360.4070709@pobox.com> References: <20050830215234.GA6991@havoc.gtf.org> <4359B12C.5020800@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail.dvmed.net ([216.237.124.58]:58297 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S932579AbVJVDfA (ORCPT ); Fri, 21 Oct 2005 23:35:00 -0400 In-Reply-To: <4359B12C.5020800@pobox.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Mark Lord Cc: linux-ide@vger.kernel.org Mark Lord wrote: > Jeff Garzik wrote: > >> >> ATAPI is getting close to being ready. To increase exposure, we enable >> the code in the upstream kernel, but default it to off (present >> behavior). Users must pass atapi_enabled=1 as a module option (if >> module) or on the kernel command line (if built in) to turn on >> discovery of their ATAPI devices. > > > Okay, I give. How do I specify this option for the case > of having libata + scsi BUILT-IN (no modules). > > I tried the usual /boot/grub/menu.lst thing: > > kernel /boot/vmlinuz-2.6.14-rc5 root=/dev/sda5 ro atapi_enabled=1 > > But still no ATAPI drive. ??? > > Hardcoding the modparm to "1" instead of "0" in libata-core.c works though. For builtin, I think the format is .parameter, thus libata.atapi_enabled=1 should work. Jeff