From owner-freebsd-arm@freebsd.org Tue Feb 6 08:31:02 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 186BEEE2CF8 for ; Tue, 6 Feb 2018 08:31:02 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 A7E707D2C4 for ; Tue, 6 Feb 2018 08:31:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 2B9D3260185; Tue, 6 Feb 2018 09:30:58 +0100 (CET) Subject: Re: Trouble with SoftIron Overdrive 1000 + USB To: Russell Haley , Jon Brawn Cc: freebsd-arm References: <79D41C3C-152C-4C58-A7AB-B2C3544DFDA3@brawn.org> <0DC0C226-DEDF-4181-9B0A-38E5CB78663A@brawn.org> From: Hans Petter Selasky Message-ID: <34f3532a-c5e4-abe4-4c38-003d38e1d383@selasky.org> Date: Tue, 6 Feb 2018 09:28:02 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2018 08:31:02 -0000 On 02/05/18 05:06, Russell Haley wrote: > usbd_setup_device_desc: getting device descriptor at addr 1 failed, > USB_ERR_TIMEOUT --> this looks like sad computer talk. I'm not a > kernel developer I think this*could* be related to the DTB file? If > an address in the flattened device tree isn't correct computers get > cranky. I know a short time back there was some device tree changes > but I don't keep up with things so I'm only speculating. Might be an IRQ problem. --HPS