> -----Original Message----- > From: G, Manjunath Kondaiah > Sent: Wednesday, March 03, 2010 7:39 AM > To: Aguirre, Sergio; linux-omap@xxxxxxxxxxxxxxx > Cc: Tony Lindgren; Shilimkar, Santosh; Raja, Govindraj > Subject: RE: [PATCH] OMAP: Zoom3: Fix Zoom3 booting issue > > > > > > To update further, it seems to be working on zoom3 with ttyS0 > > > with following combination of patches: > > > > > > 1. > > > [RFC,part2,v1,4/4] omap3: zoom 2/3: Change debugboard serial port id > > > [RFC,part2,v1,3/4] omap3: 3630sdp: Explicitly enable all UARTs > > > [RFC,part2,v1,2/4] omap3: zoom2/3 / 3630sdp: Don't init > > always all uarts > > > [RFC,part2,v1,1/4] omap2/3/4: serial: rename omap_serial_init > > > > > > 2. > > > [RESEND,PATCH/RFC] OMAP2: serial.c: Fix number of uarts in > > early_init > > > > > > 3. > > > [RFC,v3,6/6] omap3: serial: Fix uart4 handling for 3630 > > > [RFC,v3,5/6] OMAP3: PRCM: Consider UART4 for 3630 chip in > > prcm_setup_regs > > > [RFC,v3,4/6] OMAP clock: Add uart4_ick/fck definitions for 3630 > > > [RFC,v3,3/6] ARM: OMAP3630: PRCM: Add UART4 control bits > > > [RFC,v3,2/6] omap2/3/4: serial: Remove condition for > > getting uart4_phys > > > [RFC,v3,1/6] OMAP3: serial: Check for zero-based physical addr > > > > Yeah, that should be the total patchlist applied. > > > > I'm assuming you're applying from bottom to top order in your > > list above... > > Yes. But, you will be dropping v1 part2 series right? I'll just drop patch #0001 in that series, and resend. Actually, I'll group the 2 series and resend in a single batch, just to be clear on the dependency between them. Regards, Sergio > > Regards, > Manjunath -- 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
