From owner-freebsd-current@FreeBSD.ORG Fri Sep 25 08:11:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F5481065694; Fri, 25 Sep 2009 08:11:50 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2EA4F8FC18; Fri, 25 Sep 2009 08:11:48 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA12289; Fri, 25 Sep 2009 11:11:41 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4ABC7B3C.6090803@icyb.net.ua> Date: Fri, 25 Sep 2009 11:11:40 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: "Svein Skogen (listmail account)" References: <4ABA36B1.9070706@icyb.net.ua> <200909241651.47850.hselasky@c2i.net> <4ABC646D.4070604@icyb.net.ua> <4ABC7912.6070301@stillbilde.net> In-Reply-To: <4ABC7912.6070301@stillbilde.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org, Hans Petter Selasky Subject: Re: sb600/sb700 ohci experimental patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2009 08:11:50 -0000 on 25/09/2009 11:02 Svein Skogen (listmail account) said the following: > Andriy Gapon wrote: >> on 24/09/2009 17:51 Hans Petter Selasky said the following: > > *SNIP!* > >> Not sure how to interpret this. >> Either a timing issue, i.e. the register gets over-written some time after we >> program it. >> Or perhaps a bug in SMM code, i.e. when we generate an SMI (e.g. while doing >> ohci1 takeover) SMM code erroneously writes something to ohci0 ctrlhead. >> Or something else... :) > > Could it be related to "USB Legacy Devices" in bios, and thus be the > same problem that was discussed recently (regarding HZ larger than 1000)? > > An usb-legacy setup might explain both the register-changing _AND_ the > timing issue... It very well could, but... We do perform proper OHCI takeover, so we don't expect firmware to mess with the controllers after it is finished. Also, I personally have everything "USB legacy" disabled in my BIOS ("USB Legacy Support", "USB Keyboard support", "USB Mouse support"). Although, Gigabyte BIOSes are known to be sometimes smarter than they appear and to "autodetect" things when they are explicitly turned off in settings. Last point. Explaining is half the job. Fixing / working around is the other half. P.S. I am not sure what "timing issue" you referred to. -- Andriy Gapon