From: Marcel Holtmann <marcel@holtmann.org>
To: Nils Faerber <nils.faerber@kernelconcepts.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Problem with hci_usb
Date: Tue, 02 Mar 2004 20:42:32 +0100 [thread overview]
Message-ID: <1078256552.1942.194.camel@pegasus> (raw)
In-Reply-To: <1078252920.15993.117.camel@localhost>
Hi Nils,
> > Currently there is no real fix for it and once we have one, I have no
> > plans to backport it to 2.4.
>
> Why that?
> 2.4 is still the stable kernel and used by many users, so I think it
> would be worth the effort.
the current stable kernel is 2.6 and it seems that 2.4 will be closed
with 2.4.27.
> Would you accept a patch given that someone else does the backport?
For this feature you need first to backport the voice setting patch from
2.6 and you have to add the notify framework patch. Both are HCI core
changes and I think these are 2.6 changes only, but if anyone builds a
clean set of patches for 2.4 we can talk again.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-03-02 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 17:05 [Bluez-devel] Problem with hci_usb Nils Faerber
2004-03-02 17:30 ` Marcel Holtmann
2004-03-02 18:42 ` Nils Faerber
2004-03-02 19:42 ` Marcel Holtmann [this message]
2004-03-02 21:03 ` James Courtier-Dutton
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 21:47 Williams, Richard
2004-03-02 22:15 ` Marcel Holtmann
2004-03-03 0:52 ` James Courtier-Dutton
2004-03-03 12:50 Williams, Richard
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=1078256552.1942.194.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=nils.faerber@kernelconcepts.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.