From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 1/4] OMAP: DMA: Cleanup of DMA Request Lines
Date: Wed, 31 Oct 2007 06:26:24 -0700 [thread overview]
Message-ID: <20071031132624.GK32547@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D913027429025C0830@dlee13.ent.ti.com>
* Woodruff, Richard <r-woodruff2@ti.com> [071031 06:19]:
> > Let's remove the #ifdefs here, we want to be able to compile support
> for
> > 24xx and 34xx into the same kernel eventually. It's OK to have the
> same
> > DMA request channel defined in different way for 24xx and 34xx.
>
> One question here is will that happen practically? Maybe it will, not
> sure. The same sentiments were made about OMAP1 vs. OMAP2. The
> structure which results from the sharing intent perhaps is net positive
> but I don't see them converging.
>
> People would likely compiled 3430 for ARMv7 and ARMv6 for 24xx. Some
> new instructions and the like are around. I don't that its fully
> pluggable at the architecture level even.
Recent gcc allows mixing in assembly for later cores, so it's not a
problem. Sure you can optimize it for one core by not selecting anything
else.
> EABI if really used might allow some fancy solutions in theory but I
> wonder if those will develop. Not to say this the only way.
It may take a while, but let's not add any new barriers to compile in
multiple cores.
Regards,
Tony
next prev parent reply other threads:[~2007-10-31 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 7:04 [PATCH 1/4] OMAP: DMA: Cleanup of DMA Request Lines Gadiyar, Anand
2007-10-31 13:11 ` Tony Lindgren
2007-10-31 13:18 ` Woodruff, Richard
2007-10-31 13:26 ` Tony Lindgren [this message]
2007-11-21 5:12 ` Gadiyar, Anand
2007-11-21 17:06 ` Tony Lindgren
2007-11-15 1:55 ` Tony Lindgren
2007-11-15 1:57 ` Tony Lindgren
2007-11-15 4:04 ` Gadiyar, Anand
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=20071031132624.GK32547@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.