From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO stuck on a Netgear WGT634U (mips)
Date: Thu, 02 Mar 2006 21:27:59 -0700 [thread overview]
Message-ID: <4407C5CF.6060208@xmission.com> (raw)
In-Reply-To: <20060303011433.c498e85e.henryk@ploetzli.ch>
Henryk
> I'm currently trying to get btsco working on a my Netgear WGT634U
> running OpenWgt (with a lot of custom packages) on kernel 2.6.12-rc3
> and current btsco cvs. I can't seem to get it working: Each program
> that wants to play audio simply stalls (when using aplay it stops in a
> poll(), when using oss the write blocks).
very impressive. Did you have to put a hub in place since it only has
one usb port? The hub has often been a problem on x86. If you have to
use a hub, try both 1.1 and 2.0.
I'm not certain at all on the mips side of things. I've occasionally
seen complaints about bluez problems on mips but it's almost invariably
someone using kernel 2.4.
Brad
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-03-03 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 0:14 [Bluez-devel] SCO stuck on a Netgear WGT634U (mips) Henryk Plötz
2006-03-03 4:27 ` Brad Midgley [this message]
2006-03-04 1:41 ` Henryk Plötz
2006-03-04 7:47 ` Henryk Plötz
2006-03-06 7:43 ` Pieter Poorthuis
2006-03-06 8:01 ` Henryk Plötz
2006-03-06 19:10 ` Brad Midgley
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=4407C5CF.6060208@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.