From owner-freebsd-usb@FreeBSD.ORG Mon Jan 10 05:20:25 2005 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 911B316A4CE for ; Mon, 10 Jan 2005 05:20:25 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AE0543D4C for ; Mon, 10 Jan 2005 05:20:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0A5KPqO009295 for ; Mon, 10 Jan 2005 05:20:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0A5KPRS009294; Mon, 10 Jan 2005 05:20:25 GMT (envelope-from gnats) Date: Mon, 10 Jan 2005 05:20:25 GMT Message-Id: <200501100520.j0A5KPRS009294@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Julian Elischer Subject: Re: kern/71887: [kbd] Losing keyboard after plugging a bluetooth usb dongle X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Julian Elischer List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 05:20:25 -0000 The following reply was made to PR kern/71887; it has been noted by GNATS. From: Julian Elischer To: freebsd-gnats-submit@FreeBSD.org, sthommerel@osiatis.com Cc: Subject: Re: kern/71887: [kbd] Losing keyboard after plugging a bluetooth usb dongle Date: Sun, 09 Jan 2005 21:19:57 -0800 This should probably be in "doc" or somewhere.. maybe in the bluetooth handbook page. My Bt adapter also has a keyboard and mouse adapter built in and the same thing happens.. It produces the keyboard device whether or not it has found a bluetooth keyboard to attach to, so having a USB keyboard automatically over-ride teh standard keyboard in this situation is dubious at best. It probably should not be a USB PR but I can't think of a better place.. maybe the PR should just be closed and the problem documented.