public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BT-Sco
Date: Sat, 27 Nov 2004 20:07:27 -0700	[thread overview]
Message-ID: <41A940EF.6040907@xmission.com> (raw)
In-Reply-To: <41A74FE0.6020006@suche.org>

Thomas,

> here is an optimized version of btsco.c it es rewriten for Linux only.
> Is does not need libbluetooth or libasound.
> It is event driven but currently use fixed MAC
> 
> Any idea's are welcomed.

I finally looked at this. You've put some time into it I can see. If you 
look at the bug list at our sourceforge page, you'll see we actually 
want stronger ties to alsa libs (possibly using their userspace driver). 
Working toward multiple headsets is good but if the struct is global 
it's a missed opportunity.

I can understand the approach Linus takes to patches. He likes 
incremental patches that solve a single well-defined problem. It's 
easier to look for correctness.

You should choose one of the many problems with what we've got, discuss 
it here, and take a shortest-distance approach to solving it.

The unconventional stuff like "{{{" and "if(-1 == ioctl(...))" work fine 
but distract the reader from what the code is doing. After all, this 
stuff has to be read by people, not just the compiler.

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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2004-11-28  3:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 18:12 [Bluez-devel] audio problems with a2play Brad Midgley
2004-11-22 18:39 ` Marcel Holtmann
2004-11-22 18:50 ` Brad Midgley
2004-11-23  2:34   ` Henryk Plötz
2004-11-23  3:49     ` Brad Midgley
2004-11-23  5:34       ` Marcel Holtmann
2004-11-23  6:06       ` Henryk Plötz
2004-11-23  9:34         ` Marcel Holtmann
2004-11-23 19:41           ` Henryk Plötz
2004-11-23 14:20         ` Brad Midgley
2004-11-23 19:38           ` Henryk Plötz
2004-11-23 21:14             ` Marcel Holtmann
2004-11-24  2:47               ` Henryk Plötz
2004-11-24  5:24                 ` Marcel Holtmann
2004-11-23 21:34             ` Brad Midgley
2004-11-23 21:52               ` Marcel Holtmann
2004-11-24  3:16                 ` Brad Midgley
2004-11-24  5:09                   ` Marcel Holtmann
2004-11-25  5:08                     ` Henryk Plötz
2004-11-24  2:58               ` Henryk Plötz
2004-11-24  4:22                 ` Brad Midgley
2004-11-24  4:54                 ` Brad Midgley
2004-11-24  5:06                 ` Marcel Holtmann
2004-11-26 15:46               ` [Bluez-devel] BT-Sco Thomas Lußnig
2004-11-26 14:59                 ` Marcel Holtmann
2004-11-26 16:33                   ` Thomas Lußnig
2004-11-26 17:19                     ` Marcel Holtmann
2004-11-28  3:07                 ` Brad Midgley [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=41A940EF.6040907@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox