From owner-freebsd-current@FreeBSD.ORG Sat Aug 2 06:24:34 2008 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 3EF041065674 for ; Sat, 2 Aug 2008 06:24:34 +0000 (UTC) (envelope-from peter@wemm.org) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id 1D4338FC0A for ; Sat, 2 Aug 2008 06:24:33 +0000 (UTC) (envelope-from peter@wemm.org) Received: by wf-out-1314.google.com with SMTP id 24so1124693wfg.7 for ; Fri, 01 Aug 2008 23:24:33 -0700 (PDT) Received: by 10.143.8.10 with SMTP id l10mr4050282wfi.340.1217658273539; Fri, 01 Aug 2008 23:24:33 -0700 (PDT) Received: by 10.142.76.14 with HTTP; Fri, 1 Aug 2008 23:24:33 -0700 (PDT) Message-ID: Date: Fri, 1 Aug 2008 23:24:33 -0700 From: "Peter Wemm" To: "Ed Schouten" In-Reply-To: <20080801134435.GQ99951@hoeg.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080801124845.GZ1359@server.vk2pj.dyndns.org> <64491.1217595198@critter.freebsd.dk> <20080801132624.GG1359@server.vk2pj.dyndns.org> <20080801134435.GQ99951@hoeg.nl> Cc: Peter Jeremy , Poul-Henning Kamp , FreeBSD Current , FreeBSD Arch Subject: Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday 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: Sat, 02 Aug 2008 06:24:34 -0000 On Fri, Aug 1, 2008 at 6:44 AM, Ed Schouten wrote: > Hello Peter, > > * Peter Jeremy wrote: >> On 2008-Aug-01 12:53:18 +0000, Poul-Henning Kamp wrote: >> >I got a syntax error on this email Peter, didn't you mean to write: >> > >> >"Great work Ed, let me send you some patches" >> >> I would love to be able to send some patches. In order to do so, I >> need some information about how to interface with the MPSAFE TTY >> subsystem and how to adapt an existing driver. I am not the only >> person to have indicated a need for some hand-holding and I was under >> the impression that Ed would provide this but, to date, all I have is >> suggestions to look at patched drivers. > > I guess things went wrong, because I probably confused you with Peter > Wemm (I know - I'm bad with names), who inquired about si(4). I did send > him a message some time ago, to see if we could make an appointment to > discuss how we could get si(4) working. > > Even though I agree with you that we need more documentation on the TTY > layer's internals, my opinion is that other people should have shown > more interest from the start. When I sent a message a couple of weeks > ago, I almost immediately got a response from Alexander Kabaev (kan@). > He wanted to help me with the dcons(4) driver, which he did. I just > said: take a look at what I did to uart(4) and the console drivers and > gave him some random advice. He was able to send me an almost flawless > diff in a matter of hours, which he committed to the mpsafetty branch > himself! > > Maybe I'm replying to too many messages at the same time, but as John > said, it's a lot easier making the remaining drivers work after the code > has been integrated. It's not like we're permanently carving things into > stone - we've almost got a full year to get it all working again. I'll be happy to work on si(4) once the code hits the tree. Don't let si(4) get in the way. I have actual hardware (and use it 24x7), so I've got some incentive. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell