From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: Pending March patches Date: Wed, 4 Apr 2007 09:04:51 -0400 Message-ID: <20070404130449.GB29129@atomide.com> References: <460FD29D.7070707@googlemail.com> <20070403193046.GA24864@atomide.com> <20070404.102028.56387043.Hiroshi.DOYU@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20070404.102028.56387043.Hiroshi.DOYU@nokia.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: Hiroshi DOYU Cc: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org Hi, * Hiroshi DOYU [070404 03:17]: > Tony, > > I confirmed that everything is in "master" branch and the other > branches have not been updated yet, which are related to "mmu > fw"/mailbox/dspgw(?). OK, thanks for confirming. > Though I don't know how to deal with dspgw code, I guess, at least, > "mailbox" and "mmu fw" can be merged into mainline? Yes, ideally we would have DSP power on/off, mailbox, mmu fw in plat-omap. Then I suggest we move the rest of the DSP code into drivers/dsp/omap. I don't think we can get the arch/arm/plat-omap/dsp integrated to the mainline. So the chances of getting it integrated would be better under drivers/dsp/omap. What are your thoughts on that? I'm thinking that we could do it few weeks after 2.6.21 after a stable 2.6.21-omap release. > Also there's something strange. There's just small part of dsp code in > "omap-drivers", but it's only a few files, they are not enough. OK, that needs to be checked. Sounds like they should be only in master, except for DSP power on/off, mailbox and mmu fw. And those should be in omap-upstream. Regards, Tony