From owner-svn-src-all@FreeBSD.ORG Fri May 17 19:50:40 2013 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AA7D383E for ; Fri, 17 May 2013 19:50:40 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by mx1.freebsd.org (Postfix) with ESMTP id 7B7C1288 for ; Fri, 17 May 2013 19:50:40 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id at1so10141062iec.21 for ; Fri, 17 May 2013 12:50:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer:x-gm-message-state; bh=F+3Wb3pRbHtUtAmApmlCu1t8OZ5usfd/iH4VsW7xTxk=; b=UKnc6/edn/F4b8xVG4mP6qR8bxbE05YuzXZbDWvd7NT13VTKJ9pxn1IMzQ6Ew0FA75 SD26o3z9eekPEZe8dAZMtPfS39/z0mWVoM7OJSeFH9h398dB8z6PJhV2aYp74CKmLGC/ HOIK0Ulroknar64E3kNUIAZ5t7z1WVd98Q01+QwnPJuWwcysJkZTz87gglkpBpSaE4G5 vP4uoh70SJyt9jZO3GRUjFVBAKDsNNcvkGjMojxIBEom7Nw6BXrO7Ap/MCrUZ0VYItj1 IdWWB6cMscQFY8FRfEZhrhvUOtd3T+wMmVTDm0xEDkGtJAw+QXIGC/8QTIYkmkEaZG9a 7DUQ== X-Received: by 10.50.178.172 with SMTP id cz12mr13818485igc.48.1368820240058; Fri, 17 May 2013 12:50:40 -0700 (PDT) Received: from [10.69.210.64] ([137.122.64.41]) by mx.google.com with ESMTPSA id qs4sm11081821igb.10.2013.05.17.12.50.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 17 May 2013 12:50:39 -0700 (PDT) Sender: Warner Losh Subject: Re: svn commit: r250692 - head/sys/arm/conf Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 From: Warner Losh In-Reply-To: Date: Fri, 17 May 2013 15:50:36 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201305160351.r4G3p0uu047404@svn.freebsd.org> <30BAC0E1-9E8F-4FA4-A31E-C2AFAFDBCB95@freebsd.org> To: Rui Paulo X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQmsNsyWQbeAVELfIUBLH07i8llSqcavg1mne7WpIExS0q9xKLwhH56OoOtDwSspX7svqlfz Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, Tim Kientzle , src-committers@FreeBSD.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 May 2013 19:50:40 -0000 On May 16, 2013, at 9:49 PM, Rui Paulo wrote: > On 2013/05/16, at 2:02, Tim Kientzle wrote: >=20 >> I don't object, but I'm not sure why we need this. >>=20 >> I'd rather see a comment in the BEAGLEBONE >> config indicating that it can be used with >> beaglebone-black.dts. >>=20 >> Generally, I want us to move away from compiled-in >> DTBs. The BEAGLEBONE config works just fine on either >> one and it's what I plan to continue using going forward. >>=20 >> Part of the boot loader's job is to load the correct DTB. >> The images built by Crochet today already do this >> and produce images that boot on either old or new >> BeagleBone using the BEAGLEBONE config. >>=20 >> U-Boot already has logic to detect the board, >> load the correct DTB, and the same BEAGLEBONE >> kernel then runs just fine. Here are the U-Boot >> patches if you'd like to do this as well: >>=20 >> = https://github.com/kientzle/crochet-freebsd/tree/master/board/BeagleBone/f= iles >>=20 >> (There's also a copy of the compiled U-Boot and >> associated files at: >>=20 >> = http://people.freebsd.org/~kientzle/beaglebone-and-black-bootfiles.tgz >>=20 >> Moving forward, I'd like to see us generally consolidate ARM >> kernel configurations. I have some (still very experimental) >> ideas for combining the RPi and BeagleBone kernels >> into a single kernel, but with my limited time, that will >> be a fairly long-term project. If anyone's at BSDCan >> who would like to talk about it=85. I'll be at the >> "Beyond BuildWorld" session on Thursday=85. ;-) >>=20 >> Yes, this is certainly useful for people net booting >> the BeagleBone Black for developing kernel drivers, >> but I'm not sure why we would bother having it >> checked-in. >=20 >=20 > I understand your point, but what about drivers that only apply to the = BeagleBone Black, such as a driver for HDMI? Wouldn't that require a = separate kernel config file or are we expecting to use only kernel = modules? As Tim has said in another post, FDT copes very well with this. I'm glad = to see you've backed this out. But some perspective for the archives... We don't worry about this for i386/amd64 GENERIC kernels. There are the = size sensitive folks that will trim, but we have only one config file in = the base repo. Honestly, we're driving towards having *ONE* GENERIC kernel for armv6 = that can boot everywhere. While we're not there yet, we shouldn't be = doing in the opposite direction. Warner=