svn commit: r250692 - head/sys/arm/conf

[Warner Losh]

On May 16, 2013, at 9:49 PM, Rui Paulo wrote:

> On 2013/05/16, at 2:02, Tim Kientzle <kientzle at freebsd.org> wrote:
> 
>> I don't object, but I'm not sure why we need this.
>> 
>> I'd rather see a comment in the BEAGLEBONE
>> config indicating that it can be used with
>> beaglebone-black.dts.
>> 
>> 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.
>> 
>> 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.
>> 
>> 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:
>> 
>> https://github.com/kientzle/crochet-freebsd/tree/master/board/BeagleBone/files
>> 
>> (There's also a copy of the compiled U-Boot and
>> associated files at:
>> 
>> http://people.freebsd.org/~kientzle/beaglebone-and-black-bootfiles.tgz
>> 
>> 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….  I'll be at the
>> "Beyond BuildWorld" session on Thursday….  ;-)
>> 
>> 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.
> 
> 
> 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