public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-bluetooth@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [rfc]btusb with SCO support
Date: Mon, 04 Aug 2008 22:24:08 +0200	[thread overview]
Message-ID: <1217881449.7819.12.camel@californication> (raw)
In-Reply-To: <200808042032.48105.oliver@neukum.org>

Hi Oliver,

> > >>> Then why do you implement this option for hci_usb?
> > >>> And why can the other IGNORE options be overridden?
> > >>
> > >> if I wanna use the generic Bluetooth descriptor for matching, I  
> > >> need a
> > >> way to mark broken devices as to be ignored. Otherwise I would have a
> > >> really long list of matching vendor and product ids.
> > >
> > > True, but if btusb is to replace hci_usb, the module options should  
> > > match.
> > > So will you remove that option in hci_usb?
> > 
> > the override_ignore is your invention. So what do you mean?
> 
> Hm, I may be smoking strange kernels, but I copied this as far as I can tell
> from 2.6.25 hci_usb and merely renamed it because "ignore" seemed too
> generic to me. Could you check we are talking about the same parameter?

the generic ignore parameter can be removed. There is no other way to
deal with Bluetooth in Linux and we can use other ways to unattach a
driver from a device.

Regards

Marcel



  reply	other threads:[~2008-08-04 20:24 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 12:52 [rfc]btusb with SCO support Oliver Neukum
2008-07-31 14:03 ` Marcel Holtmann
2008-07-31 15:21   ` Oliver Neukum
2008-08-01 17:42     ` Marcel Holtmann
2008-08-02 23:47       ` Alan Stern
2008-08-01 10:32   ` Oliver Neukum
2008-08-01 17:43     ` Marcel Holtmann
2008-08-01 11:57   ` Oliver Neukum
2008-08-01 17:45     ` Marcel Holtmann
2008-08-04  8:33       ` Oliver Neukum
2008-08-04 16:05         ` Marcel Holtmann
2008-08-04 16:23           ` Oliver Neukum
2008-08-04 16:33             ` Marcel Holtmann
2008-08-04 17:01               ` Oliver Neukum
2008-08-04 17:25                 ` Marcel Holtmann
2008-08-04 18:32                   ` Oliver Neukum
2008-08-04 20:24                     ` Marcel Holtmann [this message]
2008-08-05 11:15                       ` Oliver Neukum
2008-08-08 21:14 ` Marcel Holtmann
2008-08-12 20:53   ` Oliver Neukum
2008-08-12 21:36     ` Marcel Holtmann
2008-08-13 15:16       ` Oliver Neukum
2008-08-13 18:23         ` Marcel Holtmann
2008-08-18 10:13     ` Marcel Holtmann
2008-08-18 12:57       ` Oliver Neukum
2008-08-18 13:38         ` Marcel Holtmann
2008-08-18 13:52           ` Oliver Neukum
2008-08-18 14:10             ` Marcel Holtmann
2008-08-18 14:27               ` Oliver Neukum
2008-08-18 14:36                 ` Marcel Holtmann
2008-08-18 14:38                   ` Oliver Neukum
2008-08-18 15:12                     ` Marcel Holtmann
2008-08-18 16:03                       ` Oliver Neukum
2008-08-18 17:07                         ` Marcel Holtmann
2008-08-18 21:26                           ` Oliver Neukum
2008-08-19  4:05                             ` Marcel Holtmann
2008-08-19  7:03                               ` Oliver Neukum
2008-08-19  7:19                                 ` Marcel Holtmann
2008-08-19  7:30                                   ` Oliver Neukum
2008-08-19  7:52                                     ` Marcel Holtmann
2008-08-19 14:49                                       ` Alan Stern
2008-08-19 15:18                                         ` Marcel Holtmann
2008-08-19 15:53                                           ` Alan Stern
2008-08-19 18:19                                             ` Marcel Holtmann
2008-08-19 18:57                                               ` Alan Stern
2008-08-20  6:39                                                 ` Dave Higton
2008-08-20 13:50                                                   ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1217881449.7819.12.camel@californication \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox