From: Matt Porter <mporter@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
Cc: Matt Porter <mporter@kernel.crashing.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: DMA support for MPC5xxx?
Date: Thu, 3 Jun 2004 11:33:02 -0700 [thread overview]
Message-ID: <20040603113302.A24468@home.com> (raw)
In-Reply-To: <20040603164245.B24A9C109F@atlas.denx.de>; from wd@denx.de on Thu, Jun 03, 2004 at 06:42:40PM +0200
On Thu, Jun 03, 2004 at 06:42:40PM +0200, Wolfgang Denk wrote:
>
> Matt,
>
> in message <20040603090635.B7347@home.com> you wrote:
> >
> > It would be nice if you could work support for your silicon into
> > the de facto standard Linux/PPC community trees like the MPC85xx
> > folks are doing.
>
> We tried. We really tried.
>
> See the thread starting at
> http://lists.linuxppc.org/linuxppc-dev/200311/msg00000.html
>
> David even posted on this list to get feedback from the community.
> But I haven't seen a single reply on the mailing lists.
So? Repost. I miss stuff the first time around a lot of times
myself [this is not to indicate that I would necessarily comment
on 5200 stuff, just an example].
> Please don't blame _us_ that the 5xxx code was not accepted for the
> public trees.
>
> This is really not fair!!!
Fair? Of course the community isn't fair. It's fickle and often
concerned only with its own current projects. Persistence really
helps when one wants something to be in the trees. Frankly, I'm
surprised that this isn't a top priority for Freescale. Maintaining
code in the kernel.org trees is far more efficient than when it
bit rots in some other tree. It also makes the support for Freescale's
silicon available to a wider audience. I think that has got to be
high on their list.
Just to add fuel to the fire, I'll note that others are able to
appear on #mklinux and work out the issues in real-time with the
folks there. is often more desirable and productive. It's also often
the only way to get Paul's attention. Oh, and FWIW, the folks working
hard on 8xx and 85xx acceptance do manage to do this.
I'm glad I don't give up as easy. It took me a while to get core OCP/4xx
in linux-2.5. :)
-Matt
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-03 18:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 10:50 DMA support for MPC5xxx? Iñigo Lopez Barranco
2004-06-03 14:54 ` David Wolfe
2004-06-03 16:06 ` Matt Porter
2004-06-03 16:42 ` Wolfgang Denk
2004-06-03 18:33 ` Matt Porter [this message]
2004-06-03 18:50 ` Tom Rini
2004-06-03 20:19 ` Sylvain Munaut
2004-06-03 20:48 ` Matt Porter
2004-06-10 19:50 ` [PATCH][RFC] MPC52xx basic support on linux 2.6 (was DMA support for MPC5xxx?) Sylvain Munaut
2004-06-18 19:20 ` Dale Farnsworth
2004-06-18 20:04 ` MPC52xx lite5200 support for booting from dBUG Dale Farnsworth
2004-06-19 10:42 ` Sylvain Munaut
2004-06-19 22:07 ` Dale Farnsworth
2004-06-19 10:55 ` [PATCH][RFC] MPC52xx basic support on linux 2.6 (was DMA support for MPC5xxx?) Sylvain Munaut
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 14:35 DMA support for MPC5xxx? Iñigo Lopez Barranco
2004-06-02 15:08 ` Wolfgang Denk
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=20040603113302.A24468@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=wd@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).