Date: Fri, 17 May 2013 15:50:36 -0400 From: Warner Losh <imp@bsdimp.com> To: Rui Paulo <rpaulo@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, Tim Kientzle <kientzle@freebsd.org>, src-committers@FreeBSD.org Subject: Re: svn commit: r250692 - head/sys/arm/conf Message-ID: <D5CA3252-8E1A-464C-9529-C27655BB042F@bsdimp.com> In-Reply-To: <F16C3146-B85F-41D4-ACE4-FC0335DD16F6@FreeBSD.org> References: <201305160351.r4G3p0uu047404@svn.freebsd.org> <30BAC0E1-9E8F-4FA4-A31E-C2AFAFDBCB95@freebsd.org> <F16C3146-B85F-41D4-ACE4-FC0335DD16F6@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 16, 2013, at 9:49 PM, Rui Paulo wrote: > On 2013/05/16, at 2:02, Tim Kientzle <kientzle@freebsd.org> 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5CA3252-8E1A-464C-9529-C27655BB042F>