From: Jon Barnett <jbarnett@pobox.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Brad Midgley <bmidgley@xmission.com>
Subject: Re: [Bluez-devel] Problems with Dell BCM2045 USB device
Date: Mon, 08 Jan 2007 15:14:26 -0500 [thread overview]
Message-ID: <1168287266.3174.3.camel@localhost> (raw)
In-Reply-To: <459BD2C1.8090208@xmission.com>
[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]
On Wed, 2007-01-03 at 08:58 -0700, Brad Midgley wrote:
> 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
I think the following patch would be sufficient (unified patch) - my
apologies for the delay but I was tied up doing something else:
----- patch code start -----
--- btsco.c 2006-10-28 10:39:27.000000000 -0400
+++ btsco.new.c 2007-01-08 13:52:52.000000000 -0500
@@ -57,6 +57,9 @@
#include <net/sock.h>
#include <net/bluetooth/bluetooth.h>
+#if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,18)
+#include <sound/typedefs.h>
+#endif
#include <sound/core.h>
#include <sound/control.h>
#include <sound/pcm.h>
----- patch code end -----
Cheers,
Jon
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-01-08 20:14 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
2007-01-08 20:14 ` Jon Barnett [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=1168287266.3174.3.camel@localhost \
--to=jbarnett@pobox.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bmidgley@xmission.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 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.