public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: Lars Grunewaldt <lgw@dark-reality.de>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] snd-bt-sco development teamup...
Date: Tue, 10 Aug 2004 00:26:04 +0200	[thread overview]
Message-ID: <1092090364.4564.46.camel@pegasus> (raw)
In-Reply-To: <4117C0AB.2010609@superbug.demon.co.uk>

Hi James,

> > I think the SCO driver should provide two interfaces. The first one we
> > know already is a socket interface to the SCO packets and the second
> > should handle the SCO packets directly over into an ALSA interface. May
> > you would like to switch between these two via an IOCTL, like we did it
> > for the RFCOMM layer.
> 
> I looked at doing ALSA -> SCO interface a long time ago, but gave up due 
> to what I considered limitations with the current bluetooth stack.

you never sent any patches for changing this. Start writing code and
send it in for review.

> To summarise, we need low latency, full duplex, and to provide that, we 
> need to accurately be able to determine and control the buffer sizes. 
> The current bluetooth stack has no api to help us in this regard, and 
> therefore will not work very well.

Actually you think that we need it, but I am still not sure that this is
really needed in case of the concept of the SCO packet from the HCI and
the SCO handling that is done on link manager/chip level. However you
can still convince me with real code.

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-08-09 22:26 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 16:51 [Bluez-devel] snd-bt-sco development teamup Lars Grunewaldt
2004-08-09 17:09 ` Marcel Holtmann
2004-08-09 17:12   ` Lars Grunewaldt
2004-08-09 17:39     ` Marcel Holtmann
2004-08-09 18:21       ` James Courtier-Dutton
2004-08-09 22:26         ` Marcel Holtmann [this message]
2004-08-09 23:53           ` Lars Grunewaldt
2004-08-10 12:14             ` Marcel Holtmann
2004-08-10 12:53               ` James Courtier-Dutton
2004-08-10 13:39                 ` Jonathan Paisley
2004-08-10 14:26                   ` Carl Orsborn
2004-08-10 14:48                     ` Marcel Holtmann
2004-08-10 15:31                     ` Jonathan Paisley
2004-08-11  8:58                       ` Roderick Taylor
2004-08-11  6:40                         ` Marcel Holtmann
2004-08-10 15:51                     ` James Courtier-Dutton
2004-08-10 18:43                       ` Jonathan Paisley
2004-08-10 19:22                         ` Carl Orsborn
2004-08-10 12:56               ` [Bluez-devel] snd-bt-sco development teamup | ALSA connection Lars Grunewaldt
2004-08-10 13:45                 ` Marcel Holtmann
2004-08-10 13:53                   ` [snd-bt-sco] " Jonathan Paisley
2004-08-10 14:36                     ` Marcel Holtmann
2004-08-10 14:39                       ` Jonathan Paisley
2004-08-10 14:21                   ` Lars Grunewaldt
2004-08-10 15:01                     ` Marcel Holtmann
2004-08-10 16:02                       ` Lars Grunewaldt
2004-08-10 14:53                   ` James Courtier-Dutton
2004-08-10 13:03               ` [Bluez-devel] snd-bt-sco development teamup Jonathan Paisley
2004-08-10 13:11                 ` Marcel Holtmann
2004-08-10 13:18                   ` Lars Grunewaldt
2004-08-10 13:20                   ` Jonathan Paisley
2004-08-10 13:22                     ` Lars Grunewaldt
2004-08-10 13:54                       ` James Courtier-Dutton
2004-08-10 13:28                     ` Marcel Holtmann
2004-08-10 13:40                   ` James Courtier-Dutton
2004-08-10 13:49                     ` Marcel Holtmann
2004-08-10 14:07                       ` James Courtier-Dutton
2004-08-10 14:34                         ` Marcel Holtmann
2004-08-10 15:15                           ` James Courtier-Dutton
2004-08-10 15:25                             ` Marcel Holtmann
2004-08-10 16:46                               ` James Courtier-Dutton
2004-08-10 22:58                                 ` Marcel Holtmann
2004-08-10 11:48           ` Lars Grunewaldt
2004-08-10 12:08             ` Marcel Holtmann
2004-08-10 12:40               ` Lars Grunewaldt
2004-08-10 13:03                 ` Marcel Holtmann
2004-08-10 13:10                   ` Lars Grunewaldt
2004-08-10 13:30                     ` Marcel Holtmann

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=1092090364.4564.46.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=James@superbug.demon.co.uk \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=lgw@dark-reality.de \
    /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