From owner-freebsd-usb@FreeBSD.ORG Thu Jan 9 15:02:40 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69BFB71 for ; Thu, 9 Jan 2014 15:02:40 +0000 (UTC) Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2B6281DF2 for ; Thu, 9 Jan 2014 15:02:40 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id i17so2688433qcy.37 for ; Thu, 09 Jan 2014 07:02:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=+Ajm2Fr6WwPnnAowwPgcoqFjNquVnezRJJivgoiVGpQ=; b=tKL1Mg39GEUdzP2C29m2HNSpLheD7Icvuiji4LZOAfKJkhn1kGfuNsMBTaIStOWkEA bF6gwt7ja1PKkioJLwQA1bUVTMhzpzGXEkc4IIxmTRcpETLlz5RtPcIEdO8IEzL+9tgU Q2ZcWBG2c4/wt7Zfi2JFx/VXgqFc/0j0ikSsYtEUnvv0DDKX+8fp8ITS4WUabpAPVvtW xLnfF7fhQ37z5S0PKFHV0fkWbu0RHwaGin3H0gwRbcgFbpH/eorNKYnNvzjivlk0u2E7 7ayZthVtrDPDwnyFnzKO3CgLejf8C2CGJ/24GNEhfOzJjiRTdEpeJmgedsX6wab8t/kE ZokA== MIME-Version: 1.0 X-Received: by 10.49.81.178 with SMTP id b18mr8749001qey.0.1389279759367; Thu, 09 Jan 2014 07:02:39 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Thu, 9 Jan 2014 07:02:39 -0800 (PST) Date: Thu, 9 Jan 2014 07:02:39 -0800 X-Google-Sender-Auth: rEUh2JOEvd3ELsFyVSsOIG3cWhQ Message-ID: Subject: USB_DEV_BCD_LTEQ() doesn't work From: Adrian Chadd To: "freebsd-usb@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 15:02:40 -0000 Hi, I'm trying to fix the atheros bluetooth USB matching to match the ath3k rules and unfortunately I'm hitting a snag. eg, in the blacklist: - { USB_VPI(0x0cf3, 0x3004, 0) }, + { USB_VPI(0x0cf3, 0x3004, 0), USB_DEV_BCD_LTEQ(1) }, Now, the rule is "if it's in the list, it's blacklisted", and in this instance, these devices with a bcdDevice of <=1 are blacklisted. However, this doesn't at all work. The USB matching code that looks like it's doing it isn't. Ideas? -adrian