From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Feb 25 09:12:45 2015 Return-Path: Delivered-To: freebsd-ports-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1791CAB4 for ; Wed, 25 Feb 2015 09:12:45 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F08A963D for ; Wed, 25 Feb 2015 09:12:44 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1P9Ci34035355 for ; Wed, 25 Feb 2015 09:12:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 198019] [PATCH]: FreeBSD 10.1 fix for comms/telldus-core Date: Wed, 25 Feb 2015 09:12:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: johan@stromnet.se X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2015 09:12:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198019 --- Comment #8 from johan@stromnet.se --- Oh, my bad. Didn't notice USB/ATTACH event matching. And.. Doh. I've been testing by doing "usbconfig -d... power_off ; ... power_on". When doing that, the USB INTERFACE ATTACH event was not sent, hence I missed it.. Looking closer, these events is what I get: Processing event '!system=USB subsystem=INTERFACE type=ATTACH ugen=ugen0.2 cdev=ugen0.2 vendor=0x1781 product=0x0c30 devclass=0x00 devsubclass=0x00 sernum="XXXX" release=0x0600 mode=host interface=0 endpoints=2 intclass=0xff intsubclass=0xff intprotocol=0xff' Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=usb/0.2.2' Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=ttyU0' Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=ttyU0.init' Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=ttyU0.lock' Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=cuaU0.init' Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=cuaU0.lock' Processing event '+uftdi0 at bus=0 hubaddr=1 port=3 devaddr=2 interface=0 vendor=0x1781 product=0x0c30 devclass=0x00 devsubclass=0x00 sernum="XXXX" release=0x0600 mode=host intclass=0xff intsubclass=0xff intprotocol=0xff ttyname=U0 ttyports=1 on uhub1' Changing to your suggestion works perfect, thanks! I'll update the patch accordingly. -- You are receiving this mail because: You are the assignee for the bug.