From owner-freebsd-arm@freebsd.org Wed Feb 21 02:18:24 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9590CF2084D for ; Wed, 21 Feb 2018 02:18:24 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3AE0B7E444 for ; Wed, 21 Feb 2018 02:18:23 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1334520CB1 for ; Tue, 20 Feb 2018 21:18:23 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 20 Feb 2018 21:18:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=KIBwFXOmyd1d49gjgy/UMD1k/YN2O NoF+bWXJrWJPFg=; b=p8cH1Fl1G5WABT9/hu+dV4fwdnrrnnKhbKr9ckpjFsUDD QxjjuGrjFcuaNUa7U9EsPJqrHNw2ZSfpNKSeK2obfxpUmuINFDeu3C0OqW8IfsA6 woVk6/P1su3Q8DfOV4ksYUtGO2Vj9DNs8EwNi6A82VCrLjdozUk1WC3Db1arvuGn fFe46q2KRduh7PDfaGsyjz3DNg5KrSKYhLx5S5eoA2hFUCP9UntVVNsLMOKgC8Uo CYCgOr1JoXCA6TIrDlXjTNO4wmuiJP7bRko+kJGGdrrbrfpjYR6mB5VXQynNWgEt RKSkeVijZuiimuBJlFioXoZB9jyjUB9pPbabPvHqg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=KIBwFX Omyd1d49gjgy/UMD1k/YN2ONoF+bWXJrWJPFg=; b=fqhYGRas+EY9atv+6j+Anj uy1365ybdV7Qb4v3J3/A/mzIp6nA090CoPZTNMWj4Y/Re4BZhCM1H7T2Zo8iqCrw 2JoWlb6989GMT1q3RhlllfjEsHeoGOQSDV/ZXEb30Za1mRqrJFTCG5jYZr+k4mGM pNlaaqH5BWUeTClKPOCAkqDjOd69pApG/D0w5AIdQZJDEYiUAMSuqzt2xAlcVaCp r0O+Pxx7Ahn9wApDEfF+II0aWpjcp0JdcR0PwngoXqHs9qlttOCybrhcsM5dSFKF VwIwyZ/axXz3O31WzsJHHUkDpWBvkZ9a6zKKDeObtJnHfuaqa3s5WePRY8T/ELuA == X-ME-Sender: Received: from desktop.zyxst.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id A04CD24519 for ; Tue, 20 Feb 2018 21:18:22 -0500 (EST) Subject: Re: Custom kernel for RPi2 and 3 To: freebsd-arm@freebsd.org References: <20180220161900.GA2345@www.zefox.net> From: tech-lists Message-ID: Date: Wed, 21 Feb 2018 02:18:21 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180220161900.GA2345@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Feb 2018 02:18:24 -0000 On 20/02/2018 16:19, bob prohaska wrote: > Does anyone have a recipe for building a custom RPi2 or RPi3 kernel? for rpi2 I comment out /remove what I don't need [0]. On rpi3 if I'll use GENERIC-NODEBUG, or comment out what's not needed. But GENERIC-NODEBUG is good and still has *some* ability to debug. I get a smaller system by adding WITHOUT= statements to various bits that will never be used in the context. man 5 src.conf > I tried it, by simply commenting out drivers I didn't recognize in > GENERIC, but after much trial-by-error the kernel didn't shrink a lot. > Having since learned that GENERIC is the tail of a much larger beast, > perhaps there's a more intelligent method. > Are you compiling on the pi? I don't because it's painfully slow and bad for the microsd. I cross-compile on a faster machine using https://github.com/freebsd/crochet - basically do this every time there's a problem/vulnerability that can't be patched and building world is needed. [0] trimming the kernel config in the wrong place can lead to compilation failure or an image that won't boot. So now I'll just remove what I'm certain it can do without. -- J.