On Wed, Feb 23, 2011 at 5:50 PM, DebBarma, Tarun Kanti <tarun.kanti@xxxxxx> wrote: >> -----Original Message----- >> From: Kishore Kadiyala [mailto:kishorek.kadiyala@xxxxxxxxx] >> Sent: Wednesday, February 23, 2011 5:37 PM >> To: DebBarma, Tarun Kanti >> Cc: Tony Lindgren; Cousson, Benoit; Gadiyar, Anand; linux-omap >> Subject: Re: Linux-next as of 20110222 broken on OMAP4 >> >> On Wed, Feb 23, 2011 at 10:20 AM, DebBarma, Tarun Kanti >> <tarun.kanti@xxxxxx> wrote: >> >> -----Original Message----- >> >> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- >> >> owner@xxxxxxxxxxxxxxx] On Behalf Of Tony Lindgren >> >> Sent: Wednesday, February 23, 2011 12:44 AM >> >> To: Cousson, Benoit >> >> Cc: Gadiyar, Anand; linux-omap >> >> Subject: Re: Linux-next as of 20110222 broken on OMAP4 >> >> >> >> * Cousson, Benoit <b-cousson@xxxxxx> [110222 04:50]: >> >> > Hi Anand, >> >> > >> >> > On 2/22/2011 10:49 AM, Gadiyar, Anand wrote: >> >> > > Looks like linux-next as of today is broken on at least OMAP4. >> >> > > >> >> > > Turning on earlyprintk, I get a crash in omap_init_mcspi. Disabling >> >> > > CONFIG_SPI_OMAP24XX gets me as far as the following lines from my >> >> > > bootup log, but I haven't attempted to debug further. >> >> > > >> >> > > If there are any patches out there to fix this, let me know. >> >> > > Else I will debug this sometime tomorrow. >> >> > >> >> > Yes, it was discussed with Tony and temporarily fixed yesterday. >> >> > >> >> > The SPI fix is is already in omap-for-linus, and the timer1 temp fix >> is >> >> below. >> >> > We need to find a better way to handle timer now that they are >> >> initialized pretty soon. >> >> >> >> I applied the fix below with Paul's ack from the other thread. >> >> So linux-next should be working again on omap4 when it gets rebuilt. >> > I have tested on OMAP4 and OMAP3. BTW, it doesn't work on OMAP24xx. >> <snip> >> >> >> The following commit breaks OMAP2420 booting >> >> git bisect bad >> 15490ef8ff8fd22d677cb5d4f6a98e5a79118dba is the first bad commit >> commit 15490ef8ff8fd22d677cb5d4f6a98e5a79118dba >> Author: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> >> Date: Wed Feb 9 16:33:46 2011 +0000 >> >> ARM: Avoid building unsafe kernels on OMAP2 and MX3 >> >> OMAP2 (armv6) and MX3 turn off support for the V6K instructions, which >> when they include support for SMP kernels means that the resulting >> kernel is unsafe on SMP and can result in corrupted filesystems as we >> end up using unsafe bitops. >> >> Re-enable the use of V6K instructions on such kernels, and let such >> kernels running on V6 CPUs eat undefined instruction faults which will >> be much safer than filesystem corruption. Next merge window we can fix >> this properly (as it requires a much bigger set of changes.) >> >> Acked-by: Tony Lindgren <tony@xxxxxxxxxxx> >> Signed-off-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> >> >> :040000 040000 48e40d2ece61dfc65cb701841efd31e3f7b2c0ff >> df6ed06ca039457b7929bdd2fe5ca9ea6a331844 M arch > I was thinking Paul's patch already tested on N800, OMAP2420! > [PATCH 0/8] OMAP2+: hwmod/clockevent: allow late-init of individual hwmods > In other words, Paul's patch fixed the breakage on OMAP24xx. > -- > Tarun > Sorry it was on lkml and not on linux-next Regards, Kishore -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
