On Tue, 16 Sep 2008 23:51:35 +0300 "ext Felipe Contreras" <felipe.contreras@xxxxxxxxx> wrote: > This is exactly the same as the overo configuration. It might make > sense to have them in a single one. > > Signed-off-by: Felipe Contreras <felipe.contreras@xxxxxxxxx> > --- > > This was suggested by Koen Kooi. > > sound/soc/omap/Kconfig | 8 ++ > sound/soc/omap/Makefile | 2 + > sound/soc/omap/omap3beagle.c | 149 +++++++++++++++++++++++++++++++++ > +++++++++ 3 files changed, 159 insertions(+), 0 deletions(-) > create mode 100644 sound/soc/omap/omap3beagle.c > Actually I've been using patched Overo driver in my Beagle for couple days now :-) However I propose to keep Beagle and Overo separated as this patch does. I think Overo can have more versatile audio connections than Beagle and thus likely to be extended over time where as Beagle audio HW is fixed as it's now. Steve, any comments? Jarkko -- 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
