All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: [Patch] Some btsco modifications
Date: Mon, 14 Mar 2005 10:26:05 -0700	[thread overview]
Message-ID: <4235C92D.80107@xmission.com> (raw)
In-Reply-To: <1110809103.5056.102.camel@pc7.dolda2000.com>

Fredrik

>>Can you comment on what the implications are for supporting multiple 
>>headsets simultaneously with a single btsco daemon? Would the kernel 
>>interaction need to be changed again or could it be limited to the daemon?
> 
> 
> Well, if you ask me, that's just unnecessary.  It would add a lot of
> complexity to the btsco daemon, for no obvious purpose. I believe that
> if one wants multiple headsets, one should simply run multiple instances
> of the btsco daemon.

Maybe what we're looking for is something to start/stop/restart 
one-per-headset btsco deamons appropriately. Maybe a daemon itself.

I will tag and merge the latest changes tonight. We will need to update 
the README (I can do this myself at some point) and Thomas or someone 
who uses it should fix btsco2.

I believe everything (with the possible glaring exception of userspace 
btsco.c) was indented to "kernel style" using some magical args to 
indent. If things work ok, I will do an indent pass again to make the 
look consistent.

Brad


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-03-14 17:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1110683934.5056.43.camel@pc7.dolda2000.com>
     [not found] ` <4233C663.80109@xmission.com>
2005-03-14  1:11   ` [Bluez-devel] Re: [Patch] Some btsco modifications Fredrik Tolf
2005-03-14 11:52     ` Lars Grunewaldt
2005-03-14 13:51       ` Fredrik Tolf
2005-03-14 15:00         ` Fredrik Tolf
2005-03-14 12:55     ` Brad Midgley
2005-03-14 14:05       ` Fredrik Tolf
2005-03-14 17:26         ` Brad Midgley [this message]
2005-03-14 19:01           ` Florian Echtler
2005-03-14 20:34             ` Brad Midgley
2005-03-15  7:22         ` Brad Midgley
2005-03-15 23:42           ` Fredrik Tolf
2005-03-16  0:17             ` Brad Midgley
2005-03-16  1:56               ` Fredrik Tolf
2005-03-16 12:30                 ` Lars Grunewaldt
2005-03-16 13:01                   ` Fredrik Tolf
2005-03-16 15:18                     ` Brad Midgley
2005-03-16 19:34                     ` 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=4235C92D.80107@xmission.com \
    --to=bmidgley@xmission.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 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.