Return-Path: Message-ID: Date: Thu, 27 Mar 2008 21:05:24 -0600 From: "Brad Midgley" To: "BlueZ users" In-Reply-To: MIME-Version: 1.0 References: <8f5c4ad0803250501x51e5cac8m7c21a6e41460c644@mail.gmail.com> <8f5c4ad0803250600q4b36a962w27e57fc3210ebd09@mail.gmail.com> <6F34AFC6-0E93-4CDD-BDFB-376BD964FCFB@holtmann.org> Subject: Re: [Bluez-users] ACL connection handle Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net Marcel As a straw man for the sco routing, would the socket option look anything like this? I'm assuming that the driver would report a socket connect failure if you specify a route that the driver can't do. --- sco.h.orig 2007-12-24 10:01:18.000000000 -0700 +++ sco.h 2008-03-27 20:57:44.000000000 -0600 @@ -45,8 +45,12 @@ /* set/get sockopt defines */ #define SCO_OPTIONS 0x01 +#define SCO_ANYROUTE 0x00 +#define SCO_HCIROUTE 0x01 +#define SCO_PCMROUTE 0x02 struct sco_options { uint16_t mtu; + uint8_t route; }; #define SCO_CONNINFO 0x02 -- Brad ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users