From: Brad Midgley <bmidgley@xmission.com>
To: jbarnett@pobox.com,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Problems with Dell BCM2045 USB device
Date: Wed, 03 Jan 2007 08:58:57 -0700 [thread overview]
Message-ID: <459BD2C1.8090208@xmission.com> (raw)
In-Reply-To: <1167793130.3356.17.camel@localhost>
Jon
> new ALSA definitions. Adding the declaration:
> #include <sound/typedefs.h>
> fixed compiling the module.
adding this in breaks compilation under 2.6.17 so btsco would need an
interested volunteer to come up with the right precompiler condition.
BCM2045 etc support has been rather hit-or-miss and I can't see what is
missing.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-03 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.341782.1167746753.8777.bluez-devel@lists.sourceforge.net>
2007-01-03 2:58 ` [Bluez-devel] Problems with Dell BCM2045 USB device Jon Barnett
2007-01-03 9:28 ` Marcel Holtmann
2007-01-03 17:05 ` Jon Barnett
2007-01-03 17:14 ` Marcel Holtmann
2007-01-03 20:04 ` Jon Barnett
2007-01-03 20:13 ` Marcel Holtmann
2007-01-03 21:56 ` Jon Barnett
2007-01-03 15:58 ` Brad Midgley [this message]
2007-01-08 20:14 ` Jon Barnett
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=459BD2C1.8090208@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jbarnett@pobox.com \
/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