Return-Path: Message-ID: Date: Wed, 26 Mar 2008 21:43:30 -0600 From: "Brad Midgley" To: "BlueZ users" In-Reply-To: <6F34AFC6-0E93-4CDD-BDFB-376BD964FCFB@holtmann.org> 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 > shouldn't be a big problem, but in general this belongs into the > kernel since userspace is not dealing with ACL and SCO/eSCO connection > handling. I'll agree it would be cleaner in kernel. If it's to be handled in the kernel then I think we need some way like an ioctl so the userspace app can tell the kernel, before opening the sco connection, whether it should happen on pcm or hci. It would be handy to have a way for the app to ask the kernel where sco is going, in case the preferred transport wasn't available. -- 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