From owner-svn-src-all@freebsd.org Mon Jan 29 13:45:52 2018 Return-Path: Delivered-To: svn-src-all@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 46D0AEC8120; Mon, 29 Jan 2018 13:45:52 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id C3F4E739D9; Mon, 29 Jan 2018 13:45:51 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 5953927395; Mon, 29 Jan 2018 13:45:48 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w0TDjWkg033454 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 Jan 2018 13:45:32 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w0TDjVcN033453; Mon, 29 Jan 2018 13:45:31 GMT (envelope-from phk) To: Oleksandr Tymoshenko cc: Emmanuel Vadot , Warner Losh , John Baldwin , Ravi Pokala , src-committers , svn-src-all@freebsd.org, svn-src-head@freebsd.org, owner-src-committers@freebsd.org Subject: Re: svn commit: r328257 - in head/sys: arm/broadcom/bcm2835 dts/arm modules In-reply-to: <20180129132736.GA66330@bluezbox.com> From: "Poul-Henning Kamp" References: <90451.1516663240@critter.freebsd.dk> <2987003.eeGRFBb6N8@ralph.baldwin.cx> <93949.1516733748@critter.freebsd.dk> <20180127210801.37b8001125dd0a2c92372f98@bidouilliste.com> <72042.1517094867@critter.freebsd.dk> <8d8ae9d10058fd72ce3ec467181c9f22@megadrive.org> <13025.1517179897@critter.freebsd.dk> <20180129063950.GA59901@bluezbox.com> <32793.1517221534@critter.freebsd.dk> <20180129132736.GA66330@bluezbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <33451.1517233531.1@critter.freebsd.dk> Date: Mon, 29 Jan 2018 13:45:31 +0000 Message-ID: <33452.1517233531@critter.freebsd.dk> X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 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: Mon, 29 Jan 2018 13:45:52 -0000 -------- In message <20180129132736.GA66330@bluezbox.com>, Oleksandr Tymoshenko writes: >> If I pick a RPI[23] out of the box, download a FreeBSD image, >> put the card in and play around, I should be able to put a >> LED in a breadboard and configure a line for PWM or attach >> an I2C or SPI device without reboot between every single >> experiment. > >No problem. We include pwm.dtbo in our snapshot and config.txt. >We have PWM running out of the box. Problem solved, no need for >any hacks. I'll gladly work with Glen and Brad to get this >functionality in snapshots/builds. You seem to have skipped the bit about "without reboot" ? >Raspberry Pi and other hobbyist ARM boards are basically Lego. >They can be turned into multiple things and that's their selling >point. They're hackers' toys. That's *exactly* why I want us to support them better. >You ignored my question: what would be authoritative source for this >kind of info? World is not perfect, FreeBSD/arm support is not perfect. >We have limited resources. Where we should apply them to guide >new contributors? At the very least have some place to point developers for a resonably up-to-date idea of what the FDT related architecture in FreeBSD is. Either documentation or source code (preferably with a bit of contextual comments) on our chosen reference platform. (Source code on ref-platform is probably more robust, as there is a better chance that it will be kept current.) >You also ignored my question about clkman fix. Provided you have >all the documentation you need [...] I don't. The information for the PWM case was based on an affine transform of information for the GPIO clock some shrewed guesses and finally in-lab measurement of what actually transpired when I frobbed registers. But more importantly, I have no idea what servies *a* clock manager offers, through which apis and to what clients and at what level of abstraction and flexibility ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.