Return-Path: Cc: linux-bluetooth@vger.kernel.org, linux-usb@vger.kernel.org Message-Id: <7B57E1E8-7077-4CCB-AF81-ACF5DCBCE918@holtmann.org> From: Marcel Holtmann To: Oliver Neukum In-Reply-To: <200808041033.05446.oliver@neukum.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v928.1) Subject: Re: [rfc]btusb with SCO support Date: Mon, 4 Aug 2008 18:05:11 +0200 References: <200807311452.24166.oliver@neukum.org> <200808011357.16868.oliver@neukum.org> <1217612718.7819.7.camel@californication> <200808041033.05446.oliver@neukum.org> Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Oliver, >>> >>> +module_param(override_ignore, bool, 0644); >>> +MODULE_PARM_DESC(override_ignore, "Drive blacklisted devices"); >> >> Why do we need this one? What is it good for? > > To override HCI_IGNORE. IF we provide overrides for blacklist entries, > it should be done systematically. no we should not do that. The HCI_IGNORE is for devices that pretend to be Bluetooth H:2 compatible, but they are not. In these cases we do have other drivers that do this right. See bcm203x and bpa10x drivers. Regards Marcel