public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Santarelli <hrk@users.sourceforge.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: marcel@holtmann.org, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bluetooth usb hci: ISSC usb dongle with buggy SCO  support
Date: Tue, 9 Dec 2008 20:22:27 +0100	[thread overview]
Message-ID: <42AA6D4E-DCE6-487B-9B70-2B0A7EFA76EC@users.sourceforge.net> (raw)
In-Reply-To: <F469DC97-2EE0-4CE5-BB1C-7419B8A31985@users.sourceforge.net>


Il giorno 09/dic/08, alle ore 00:07, Luca Santarelli ha scritto:

>
> Il giorno 07/dic/08, alle ore 09:19, Andrew Morton ha scritto:
>
>> linux-next has:
>>
>> commit 12421b40b81d101d7535e03f1af197365adc932b
>> Author: Marcel Holtmann <marcel@holtmann.org>
>> Date:   Sun Nov 30 12:17:21 2008 +0100
>>
>>   Bluetooth: Remove deprecated hci_usb driver
>>
>>   The old hci_usb driver has been fully replaced with the new btusb  
>> driver
>>   and all major distributions switched to the new driver now. This  
>> removes
>>   it since it should not be used at all anymore.
>>
>> so please confirm that btusb correctly supports that hardware?
>
>
> Thanks for the heads up! I'll compile the new sources and let you  
> know if it's supported. However, since the hci_usb is being  
> deprecated but not removed, shouldn't the patch be incorporated  
> nonetheless?
>
> Luca

Ok, I'm back. I compiled the latest sources and the device is  
recognized and works with the new btusb driver. What about the  
deprecated driver? Will it be fixed or kept as it is?

Luca

  parent reply	other threads:[~2008-12-09 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 23:02 [PATCH] bluetooth usb hci: ISSC usb dongle with buggy SCO support Luca Santarelli
2008-12-07  8:19 ` Andrew Morton
2008-12-07 12:58   ` Daniel Drake
2008-12-08 23:07   ` Luca Santarelli
2008-12-09 13:49     ` Markos Chandras
2008-12-09 19:22     ` Luca Santarelli [this message]
2008-12-09 12:31   ` Markos Chandras

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=42AA6D4E-DCE6-487B-9B70-2B0A7EFA76EC@users.sourceforge.net \
    --to=hrk@users.sourceforge.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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