public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jonathan Paisley <jp@dcs.gla.ac.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 15:28:27 +0200	[thread overview]
Message-ID: <1092144507.4564.125.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.59.9999.0408101412470.22497@brava.dcs.gla.ac.uk>

Hi Jonathan,

> > the point is that dropping packets and generating zero packets is
> > already part of the Bluetooth chip. This means we will get a correct
> > stream from the hardware and we must only make sure that we deliver our
> > packets in time as long as the hardware is able to buffer it.
> 
> Agreed. The problem I've seen is due to the driver not providing packets 
> in time to the SCO layer. As such, the hardware doesn't get a chance to 
> buffer.

there is also a flow control for SCO packets if my memory don't play
tricks with me. However I think that we should not worry about this too
much at the moment. If we ran into problems then we can think about how
we can fix them.

> > I prefer the ALSA integration would be written from scratch, because the
> > original driver was written for a 2.4 kernel and we must concentrate on
> > the 2.6 series. The ALSA subsytem will be cleaned up in the next kernel
> > releases and the magic casting stuff they do is still wrong.
> 
> I haven't been keeping track of ALSA development recently. It sounds like 
> you're saying that the API is going to be changing enough that simple 
> modifications to the existing ALSA-interfacing code in snd-bt-sco will not 
> be enough to keep it up to date. Does this mean it would be worth putting 
> a hold on development of a properly-bluez-integrated driver until the ALSA 
> subsystem has stabilised?

I don't know how much of the API will be really changed, but actually
some parts can be done much easier. My point is that I get a clean
driver in the end. The focus is the ALSA of a recent 2.6.8 kernel or
later and nothing before. If we must change something in the ALSA
library or tools only for adding another driver, this is a sign that
something has designed in a wrong way.

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

  parent reply	other threads:[~2004-08-10 13:28 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
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 [this message]
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=1092144507.4564.125.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=jp@dcs.gla.ac.uk \
    --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