From owner-freebsd-mips@FreeBSD.ORG Mon Mar 15 21:23:40 2010 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42C671065672 for ; Mon, 15 Mar 2010 21:23:40 +0000 (UTC) (envelope-from ray@ddteam.net) Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com [209.85.218.216]) by mx1.freebsd.org (Postfix) with ESMTP id D0D848FC19 for ; Mon, 15 Mar 2010 21:23:39 +0000 (UTC) Received: by bwz8 with SMTP id 8so3382915bwz.3 for ; Mon, 15 Mar 2010 14:23:38 -0700 (PDT) Received: by 10.204.20.77 with SMTP id e13mr3334049bkb.163.1268688218139; Mon, 15 Mar 2010 14:23:38 -0700 (PDT) Received: from localhost (240-142-132-95.pool.ukrtel.net [95.132.142.240]) by mx.google.com with ESMTPS id 16sm3165428bwz.1.2010.03.15.14.23.35 (version=SSLv3 cipher=RC4-MD5); Mon, 15 Mar 2010 14:23:36 -0700 (PDT) Date: Mon, 15 Mar 2010 23:22:20 +0200 From: Alex RAY To: "M. Warner Losh" Message-Id: <20100315232220.7242063e.ray@ddteam.net> In-Reply-To: <20100315.082334.1032464807170521414.imp@bsdimp.com> References: <20100314.181902.67053632336017068.imp@bsdimp.com> <20100315111756.05fd5805.ray@ddteam.net> <20100315.082334.1032464807170521414.imp@bsdimp.com> Organization: DDTeam.net X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: mips@FreeBSD.org Subject: Re: Request for review: AR71XX config cleanup X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2010 21:23:40 -0000 On Mon, 15 Mar 2010 08:23:34 -0600 (MDT) "M. Warner Losh" wrote: > In message: <20100315111756.05fd5805.ray@ddteam.net> > Alex RAY writes: > : Maybe umass and SCSI modules relocate from the std files to config files? > > I'm a little on the fence here. > > std.foo is supposed to have all the things that are in GENERIC. In > fact, I see sys/i386/GENERIC eventually being: > > ident GENERIC > include "std.i386" > > So, if we view it from that point of view, it becomes clear that we > want to include the usb/scsi stuff in std.ar71xx. They are easy > enough to omit if you had a system without usb: > > include "std.ar71xx" > nodevice usb > nodevice umass > nodevice scbus > nodevice da > > wouldn't be a horrible burden on people. > > But then again, USB on x86 includes everything, whereas I've only > include umass. If I'm going to subset, why this subset. How would > others know what the right subset would be for their boards, etc. > > So that's why I'm on the fence. Once you start getting into the "this > is sensible" game, then you have to start making seasoned judgements. > Without a better definition of what a 'generic' kernel should have, > or shouldn't have, I'm not sure there's a better way. > > Warner I think it should do two types of config, one for SoC, the second for the boards on it. First - just SoC can (in my BCM5354 cc, bfe, usb, wifi) Second - what board need GPIOs (btn, LED, etc), flash partitions mapping etc. Then std files hold SoC family defaults. (BCM5354, BCM4704 and BCM5836 very similar, so share one std file ) like so: mips/conf/D-LINK_DIR-320 (include mips/conf/BCM5454) mips/conf/ASUS_WRGXXXX (include mips/conf/BCM5354) mips/conf/BCM5354 (include mips/bcm47xx/std.bcm) . . . - Alex RAY