From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yegor Yefremov Subject: Re: AM3517evm Date: Thu, 15 Mar 2012 16:52:40 +0100 Message-ID: <4F621048.2090003@visionsystems.de> References: <4F5E0036.105@visionsystems.de> <20120315154335.GA29645@animalcreek.com> Reply-To: yegor_sub1@visionsystems.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from hhlx01.visionsystems.de ([62.145.30.242]:52868 "EHLO mail.visionsystems.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760965Ab2COPwz (ORCPT ); Thu, 15 Mar 2012 11:52:55 -0400 In-Reply-To: <20120315154335.GA29645@animalcreek.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Mark A. Greer" Cc: "George C. Huntington, III" , linux-omap@vger.kernel.org, mporter@ti.com Am 15.03.2012 16:43, schrieb Mark A. Greer: > On Mon, Mar 12, 2012 at 02:55:02PM +0100, Yegor Yefremov wrote: >> Am 09.03.2012 18:22, schrieb George C. Huntington, III: >>> I would like to make the newer kernel (3.x) work with the AM3517EVM. >>> I have a 2.6.32 and a 2.6.33 that run well on the board, but the >>> recent kernels have kernel panics before even running init. where >>> should I start? is there a better place to pursue this? >> Have you tried this one? http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=summary >> >> I have this one booting one month ago, but I checked out the kernel today and it hangs somewhere: >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. > This looks like you have your console device set to ttyS2 instead of ttyO2. > > Which branch of that repository did you use? My kernel params: CONFIG_CMDLINE="root=/dev/mmcblk0p2 rootwait console=ttyO2,115200" and I force them, so bootloader has nothing to say. I'm using master branch. Yegor