From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Tue, 14 Apr 2015 08:06:20 -0600 Subject: [U-Boot] [PATCH v6 00/15] Add PSCI support for Jetson TK1/Tegra124 + CNTFRQ fix In-Reply-To: <20150414134636.GH16702@bill-the-cat> References: <20150414134636.GH16702@bill-the-cat> Message-ID: <552D1EDC.7060307@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 04/14/2015 07:46 AM, Tom Rini wrote: > On Mon, Apr 13, 2015 at 06:48:05AM +0200, Jan Kiszka wrote: > >> Changes in v6: >> - rebased over master >> - included Thierry's SMMU enabling patch >> - moved activation patch at the end so that it can be held back >> >> This version can also be found at >> https://github.com/siemens/u-boot/tree/jetson-tk1-v6. > > So what level of coordination do we need on applying this series so that > kernels (both old and new) can continue to function? And perhaps README > updates or similar? Thanks! Hopefully this series doesn't change anything by default, and simply allows people to turn on support for booting kernels in non-secure mode if they want to? If so, there shouldn't be any co-ordination required. If it changes the default behaviour, co-ordination is probably required, and that'd be a bad thing.