All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javi F Gorostiza <ingestado@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] patch for 2.6.>23 kernels or how to
Date: Fri, 06 Jun 2008 21:16:22 +0200	[thread overview]
Message-ID: <48498D06.4010402@gmail.com> (raw)

Hello, I have tried to use plugz that I download from
bluetooth-alsa.sourceforge site using the last kernel: 2.6.25. It does
not give any error (compiling the kernel or using headsetd) but anything
happens: I can't connect the BT-headset to the headsetd, using asound.rc
It worked pretty well in 2.6.23, using the patch found in the plugz
distribution. Is it necessary another patch to the kernels that are
2.6.>23 (2.6.24 or 2.6.25)?
Thanks a lot,
J

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

                 reply	other threads:[~2008-06-06 19:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=48498D06.4010402@gmail.com \
    --to=ingestado@gmail.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 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.