From: Tony Lindgren <tony@atomide.com>
To: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Pending March patches
Date: Wed, 4 Apr 2007 09:04:51 -0400 [thread overview]
Message-ID: <20070404130449.GB29129@atomide.com> (raw)
In-Reply-To: <20070404.102028.56387043.Hiroshi.DOYU@nokia.com>
Hi,
* Hiroshi DOYU <Hiroshi.DOYU@nokia.com> [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
next prev parent reply other threads:[~2007-04-04 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 15:41 Pending March patches Dirk Behme
2007-04-02 6:21 ` Hiroshi DOYU
2007-04-03 19:30 ` Tony Lindgren
2007-04-04 7:20 ` Hiroshi DOYU
2007-04-04 13:04 ` Tony Lindgren [this message]
2007-04-04 14:10 ` Hiroshi DOYU
2007-04-04 14:36 ` Tony Lindgren
2007-04-10 7:36 ` Pending March patches -- OMAP DPSGW code migration Hiroshi DOYU
2007-04-10 19:56 ` Paul Mundt
2007-04-20 21:31 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070404130449.GB29129@atomide.com \
--to=tony@atomide.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox