* Kanigeri, Hari <h-kanigeri2@xxxxxx> [100420 15:03]: > Felipe, > > > -----Original Message----- > > From: Felipe Contreras [mailto:felipe.contreras@xxxxxxxxx] > > Sent: Tuesday, April 20, 2010 4:49 PM > > To: Kanigeri, Hari > > Cc: linux-omap@xxxxxxxxxxxxxxx; Shilimkar, Santosh; Hiroshi DOYU; > > tony@xxxxxxxxxxx > > Subject: Re: [PATCH 1/3][v2] OMAP:iommu support for OMAP4 > > > > On Wed, Apr 21, 2010 at 12:31 AM, Kanigeri, Hari <h-kanigeri2@xxxxxx> > > wrote: > > > From 9a6f91b0c108fd010afdb6bddcae92579c87fcbd Mon Sep 17 00:00:00 2001 > > > From: Hari Kanigeri <h-kanigeri2@xxxxxx> > > > Date: Tue, 20 Apr 2010 12:03:03 -0500 > > > Subject: [PATCH 1/3] OMAP:iommu support for OMAP4 > > > > > > This patch provides the iommu support for OMAP4 co-processors. > > > This includes changes to omap3-iommu.c file to make it generic > > > for all OMAPs. Renamed omap3-iommu.c to omap-iommu.c > > > > This smells like two patches: one that moves omap3-iommu to > > omap-iommu, and another one that adds omap4 support. > > > > But unfortunately this would break multi-omap support. I think both > > omap3 and omap4 devices should be there, and selected at run-time. > > > > -- I am not sure as why this would break multi-omap support. We would select either OMAP3 or OMAP4 specific structures at compile time based on the platform selected, and rest of the code is same for both OMAP3/4. We can compile and boot omap2 + omap3 + omap4 with the same kernel, see omap3_defconfig. Tony -- 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
