From owner-freebsd-usb@FreeBSD.ORG Wed Aug 20 21:07:24 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CEBB106566B for ; Wed, 20 Aug 2008 21:07:24 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4FD828FC16 for ; Wed, 20 Aug 2008 21:07:24 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 30ADB1A4D80; Wed, 20 Aug 2008 14:07:24 -0700 (PDT) Date: Wed, 20 Aug 2008 14:07:24 -0700 From: Alfred Perlstein To: Peter Jeremy Message-ID: <20080820210724.GZ16977@elvis.mu.org> References: <20080818205914.GJ16977@elvis.mu.org> <200808191758.22981.hselasky@c2i.net> <48AB233C.2010602@FreeBSD.org> <200808192219.19246.hselasky@c2i.net> <20080820074205.GC32539@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080820074205.GC32539@server.vk2pj.dyndns.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb4bsd patch review [was Re: ...] X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2008 21:07:24 -0000 * Peter Jeremy [080820 09:32] wrote: > On 2008-Aug-19 22:19:14 +0200, Hans Petter Selasky wrote: > >On Tuesday 19 August 2008, Kris Kennaway wrote: > >> Hans Petter Selasky wrote: > >> > On Tuesday 19 August 2008, Alfred Perlstein wrote: > >> >> need to wait for smp tty code. > >> > > >> > If this requires changes in the USB serial port drivers there will be > >> > trouble. > >> > >> I am not sure what you mean by this statement, since it can be > >> interpreted in several ways, some not so friendly. > > > >I mean I need to make another patchset. And that the current patchset will > >break the kernel compilation if blindly committed after mpsafetty. > > I am concerned that the current plans appear to have both mpsafetty > and usb4bsd committed at virtually the same time. With the best will > in the world, it's still likely that one or both imports will have > some rough edges. IMHO, there should be a reasonable period between > major kernel subsystem upheavals to allow things to stabilise. Having > both a new USB stack and a new TTY subsystem would appear to make it > unnecessarily difficult to identify the cause of USB serial port > issues. Again, the usb2 code is completely optional, you won't see any changes unless you change your kernel config file to use the "usb2" stack. This is sort of like oldcard/newcard, you pick and choose. -- - Alfred Perlstein