All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco crash without daemon
Date: Sun, 16 Jan 2005 18:10:11 +0100	[thread overview]
Message-ID: <41EA9FF3.5090900@dark-reality.de> (raw)
In-Reply-To: <41EA44F4.50606@egabriel.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ligi wrote:
|
| | Why do you want to use the external alsa-driver anyway?
| |
| It recommended to use the external Driver in the Gentoo docs - and i
| found nothing in the btsco docs that says something diffrent - so i
| used the external Driver ( Well -  I like the external Driver Concept
| (in a world with so much devices ) more too .... )

well, we want to migrate the snd-bt-sco to userspace if possible, so you
won't need a specific alsa driver (kernel vs. standalone) sooner or
later, hopefully. But until than it's the easiest way (and the proper
way) to use kernel alsa as a reference, not the standalone alsa (the
kernel is available on any system, isn't it? ;)

I ran into some problems myself when I was using btsco on a system that
had an unsupported audio device that needed a driver patched into alsa
(no patch for the kernel available) AND that was written in C++ so very
bad mojo. I hacked in into the kernel, got bad voices from lkml (*vbeg*)
for using c++ in kernel space and stuff. Well was fun. The point beeing:
meanwhile this driver has been re-implemented in C and there's a kernel
patch so it can easily used with alsa-kernel.

| PS: You can mark the SouthWing NeoVoice Headset ( on a Sitecom USB ->
| BT Dongle ) as working for btsco - there is no wiki so I cant do this
| now !-)
| btw. anyone interested in a btscoWiki ?

Sounds good for me, it would make changing the site a lot easier, would
it not? Any more comments from i.e. Brad?

Of course an "external resource site" is possible even if we don't want
to have an official wiki ;)

best regards,
~  Lars

- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB6p/yQWC6DTWkDAoRAuRUAKCImgzbBTD/5PhqzRKUSRJAgce1SQCeNEWQ
ff5CCb1DTfXrk21W9n05SAQ=
=nx+Z
-----END PGP SIGNATURE-----


-------------------------------------------------------
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-16 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 13:32 [Bluez-devel] btsco crash without daemon ligi
2005-01-15 14:17 ` Lars Grunewaldt
2005-01-15 14:45   ` ligi
2005-01-15 15:19     ` Lars Grunewaldt
2005-01-15 18:59       ` ligi
2005-01-16  0:32         ` Lars Grunewaldt
2005-01-16 10:41           ` ligi
2005-01-16 17:10             ` Lars Grunewaldt [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=41EA9FF3.5090900@dark-reality.de \
    --to=lgw@dark-reality.de \
    --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.