From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <44BF9F02.2040103@xmission.com> Date: Thu, 20 Jul 2006 09:19:30 -0600 From: Brad Midgley MIME-Version: 1.0 To: BlueZ users References: <44BE9DE5.7000000@over-here.org> <20060719214242.GA20848@adamis.de> <44BECE23.8080004@xmission.com> <20060720145130.GA19833@adamis.de> In-Reply-To: <20060720145130.GA19833@adamis.de> Subject: Re: [Bluez-users] Problems with Ambicom BT-2000E 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 Mathias > However it wouldn't be that bad not having to patch each new kernel > again and again... maybe you know some contact to get this thing solved? I don't know anyone like that--sorry. One reason I think it got overlooked is you claimed to support hardware that you didn't have around to test. Keep the scope and impact limited and if it supports something new as a side effect, you may want to keep that under your hat if you don't have someone to test it. The other route you can go is ask a vendor to support it. I think ubuntu is in a good position for that. If people start to benefit from a vendor patch, the kernel guys may see it differently. 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-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users