From owner-freebsd-usb@FreeBSD.ORG Thu Dec 2 10:20:13 2004 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9767916A4CE for ; Thu, 2 Dec 2004 10:20:13 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (84-72-27-39.dclient.hispeed.ch [84.72.27.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id A611D43D5A for ; Thu, 2 Dec 2004 10:20:09 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:5448:1b27:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id iB2AK0R19933 verified NO) for ; Thu, 2 Dec 2004 11:20:03 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id iB2AJxi19931; Thu, 2 Dec 2004 11:19:59 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Thu, 2 Dec 2004 11:19:59 +0100 (CET) Message-Id: <200412021019.iB2AJxi19931@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma References: <200410201612.i9KGClg05229@Mail.NOSPAM.DynDNS.dK> <200411301310.iAUDAJl01186@Mail.NOSPAM.DynDNS.dK> <20041130181603.A1352@curly.tele2.no> <200412010727.iB17RCT07496@Mail.NOSPAM.DynDNS.dK> <41AE5985.10401@elischer.org> To: freebsd-usb@freebsd.org Subject: Re: USB OHCI problems... X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 10:20:13 -0000 Julian Elischer asked of me... > >my present 4.x USB stack comes from -current as it is. Many thanks! > I'm intrigued.. with good reason, i may add > why do you have a 4.x system with a 5.x USB stack? Hysterical raisins, mostly, if you ask me. Some many months back, Ian Dowse announced his P4 work as a patchset to -current, which sounded like it addressed many of the USB problems I had been experiencing. So, I took that and merged it as best I could with my system, borrowing from -current when needed. Sometime around this time, you also did work to bring the 4.x USB code more in line with current. Since your mega-merge, I've seen a few commits to -current USB while 4.x code has gone mostly untouched. As I discover more problems (mostly OHCI-related), I figure the best thing is for me to try out the latest code, as due to my mostly-offline status, I can only make large incremental updates, that are not so easy to keep track of -- then I can see if the problem is solved there. Also, FWIW, it appears that my ehci.c that I compiled was taken directly from NetBSD, as I had still experienced data-toggle problems with all FBSD source of that time, while they were less frequent (though occasionally present) with NetBSD. My last source update was made late October, before the latest recent updates. At that time, I didn't notice any 4.x updates of interest since May or so. I'm going to see if I can solve my known USB/OHCI issues with the code I have, then if so, I'll set this aside and try out clean 4.x source, in order to try and reduce the differences between my source and that released, but without having to suffer through bugs that may still affect me in original 4.x code. And in particular, the if_axe code I was trying to get working some weeks/months ago was only present in -current, and part of what I tried in order to avoid the panics I saw was to try and use as much -current code as possible to minimize differences. Oh, and most importantly, because I don't have the foggiest idea what I'm doing, so doing things all wrong is a good way to help me learn. next question? barry bouwsma (sheesh, ask a quick question, get a novel in response)