From owner-cvs-all Sun Feb 21 14:52:47 1999 Delivered-To: cvs-all@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6F3AE10FFF for ; Sun, 21 Feb 1999 14:52:43 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA20563; Sun, 21 Feb 1999 14:47:06 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdJ20559; Sun Feb 21 22:47:03 1999 Date: Sun, 21 Feb 1999 14:46:41 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , Larry Lile , "Daniel C. Sobral" , cvs-all@FreeBSD.ORG Subject: Re: Current status of the olicom fracas. In-Reply-To: <57188.919625674@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk When core considers this. I think they should consider the following layout.. The two firmware file should be recoded into 'c'. (byte 0x03, .....) They and the i386 .o file should be moved to contrib/sys/oltr/oltr_i386.o.uu The readme should be there also. On Sun, 21 Feb 1999, Jordan K. Hubbard wrote: > I think we're going in circles on this argument right now and I'd like > to simply leave things as they are until more people in core have had > the chance to comment. I'm specifically interested in David's > reaction since we may need him to play "tie breaker" on this one, but > David is also at OSDI in New Orleans at the moment and probably hasn't > seen any of this discussion. Since he's our principal architect and > the guy we elected to have final say on contraversial issues exactly > like this one (I don't see a core team concensus coming together on > this yet but maybe one will and DG won't even have to break a tie), > we need to get his input before any final "ruling" on this is > made. Given the mixed reactions I've seen so far on this issue, it > may well wind up being his decision by default. > > - Jordan > > > In message , Larr > y > > > > >So are my suggestions for making my driver and Olicom's objects more > > >palatble to the source tree not acceptable? What are the points of > > >contention? I would like to know so that I can see what else I could > > >do to fix this. > > > > They are not acceptable to me. An object file just simply doesn't > > count as "source" in my book. > > > > >I do think it is important to make the distinction between my driver > > >"if_oltr.c" and Olicom's "trlld.o". There is nothing about my driver, or > > >Olicom's header file "trlld.h", that violate the spirit of the source > > >tree. I think that the driver and header are fine where they live in > > >dev/oltr as it is a combined ISA/PCI driver. > > > > Sure, it's only that one file I have a problem with, and only because > > we do not have the source. > > > > -- > > Poul-Henning Kamp FreeBSD coreteam member > > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > > FreeBSD -- It will take a long time before progress goes too far! > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message