From: "Fritz Code" <codefritz@googlemail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] old patches - where to get from?
Date: Mon, 18 Aug 2008 15:22:09 +0200 [thread overview]
Message-ID: <3e9cdced0808180622k6185e215k6017ce2ba0cadd15@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 564 bytes --]
I would like to get the patch to provide bluez bluetooth support for Kernel
2.4.21.
Some weeks ago this patch was available at bluez.org or
holtmann.org.Unfortunately it isn't anymore.
And can anybody tell me what this patch makes? I guess it provides support
for additional bluetooth devices as far as I kown for the AVM bluefritz usb
dongel?
Any other changes?
Another question: Why is the bluetooth bluez subsystem distributed in the
two folders drivers/bluetooth and net/bluetooth?
So at which location is what implemented?
Thanks,
--
Regards,
--Codefritz
[-- Attachment #1.2: Type: text/html, Size: 725 bytes --]
[-- Attachment #2: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2008-08-18 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 13:22 Fritz Code [this message]
2008-08-19 7:00 ` [Bluez-users] old patches - where to get from? Marcel Holtmann
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=3e9cdced0808180622k6185e215k6017ce2ba0cadd15@mail.gmail.com \
--to=codefritz@googlemail.com \
--cc=bluez-users@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