public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Multiple Headsets
Date: Tue, 11 Jan 2005 11:15:32 +0100	[thread overview]
Message-ID: <1105438532.8056.12.camel@pegasus> (raw)
In-Reply-To: <41E39BC8.2020105@xmission.com>

Hi Brad,

> I would be happy to document it, but I'm not sure exactly what Marcel 
> did. If the number of headsets is fixed at module insertion time then it 
> sounds like it's just good for testing.

with a 2.6 kernel you can change a kernel module parameter on the fly
from /sys/module/ and then you only have to re-plug your dongle to
activate the new settings.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-01-11 10:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 10:54 [Bluez-devel] Multiple Headsets Jeff Fern
2005-01-10 11:32 ` Lars Grunewaldt
2005-01-10 13:02   ` Marcel Holtmann
2005-01-10 16:14     ` Lars Grunewaldt
2005-01-11  9:26       ` Brad Midgley
2005-01-11 10:15         ` Marcel Holtmann [this message]
2005-01-11 10:30           ` Lars Grunewaldt
2005-01-11 16:27             ` Brad Midgley
2005-01-11 16:37               ` Marcel Holtmann
2005-01-11 16:55               ` Lars Grunewaldt
2005-01-12  1:47                 ` Lars Grunewaldt
2005-01-16 19:49   ` Jeff Fern
2005-01-16 20:41     ` Lars Grunewaldt

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=1105438532.8056.12.camel@pegasus \
    --to=marcel@holtmann.org \
    --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