From: 王晋伟 <yibanbano@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dpd produces choppy audio with Digitus dongle, OK with D-Link
Date: Mon, 9 Apr 2007 11:18:03 +0800 [thread overview]
Message-ID: <38338cf00704082018q652cc399o73c2f7bc16d984b1@mail.gmail.com> (raw)
In-Reply-To: <4617D0EE.6060006@yahoo.com.au>
[-- Attachment #1.1: Type: text/plain, Size: 494 bytes --]
>
> hey
>
Does anyone know where to download the bluez kernel patch?i want to
> download the 2.6.14-mh2 and 2.6.18-mh2. In www.bluez.org,i can only find
> the kernel 2.4 bluez patch and 2.6.20-mh1;and in
> http://www.holtmann.org/linux/kernel/, i can't find that ;aslo i can't
> google it.
who can tell me the download addresses or send to me ? thanks .
walson
2007.4.9
[-- Attachment #1.2: Type: text/html, Size: 1678 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-09 3:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 16:12 [Bluez-devel] a2dpd produces choppy audio with Digitus dongle, OK with D-Link bluez.mexon
2007-03-09 18:13 ` Brad Midgley
2007-03-09 19:13 ` [Bluez-devel] a2dpd produces choppy audio with Digitus dongle, (bluez: message 14 of 20) " bluez.mexon
2007-04-07 17:12 ` [Bluez-devel] a2dpd produces choppy audio with Digitus dongle, " bluez.mexon
2007-04-09 3:18 ` 王晋伟 [this message]
2007-03-10 16:38 ` Robert Huitl
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=38338cf00704082018q652cc399o73c2f7bc16d984b1@mail.gmail.com \
--to=yibanbano@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/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