From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] old patches - where to get from?
Date: Tue, 19 Aug 2008 09:00:01 +0200 [thread overview]
Message-ID: <1219129201.7591.73.camel@violet.holtmann.net> (raw)
In-Reply-To: <3e9cdced0808180622k6185e215k6017ce2ba0cadd15@mail.gmail.com>
Hi,
> 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?
the 2.4 kernel is no longer supported. That is an ancient kernel. You
should not be using that one.
> 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?
I think that is quite clear. Protocols in net/bluetooth and drivers in
driver/bluetooth.
Regards
Marcel
-------------------------------------------------------------------------
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=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-08-19 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 13:22 [Bluez-users] old patches - where to get from? Fritz Code
2008-08-19 7:00 ` Marcel Holtmann [this message]
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=1219129201.7591.73.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--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