linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@KERNEL.CRASHING.ORG>
To: Sylvain Munaut <tnt@246tnt.com>
Cc: Tom Rini <trini@KERNEL.CRASHING.ORG>, linuxppc-dev@lists.linuxppc.org
Subject: Re: DMA support for MPC5xxx?
Date: Thu, 3 Jun 2004 13:48:04 -0700	[thread overview]
Message-ID: <20040603134804.B24468@home.com> (raw)
In-Reply-To: <40BF87BB.4020808@246tNt.com>; from tnt@246tnt.com on Thu, Jun 03, 2004 at 10:19:07PM +0200


On Thu, Jun 03, 2004 at 10:19:07PM +0200, Sylvain Munaut wrote:
>
>  >>> 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].
>  >
>  >
>  > And this time do it against 2.6.  Even if 2.4 wasn't necessarily
>  > frozen at the time we first tried, it is now.
>
> Actually I got some patch to support MPC5200 ( and only this one, no
> mgt5100 stuff ) for 2.6
> It only supports booting, serial console and i2c. Not much but could
> that be put in official tree if I submit it ? Or does it need to
> support  more than that to worth inclusion.
> So that at least if someone tries to implement more ( I'll resume my
> work on it in a few weeks ), it has a base already in official tree.

Why not? You're the only one showing interest in supporting 5200 in
2.6. Post the patch and if it's clean it can go in. The "i2c", I
assume, is an i2c host adapter driver so that needs to be separated
so it can go to gregkh. Don't lump it in with the include/asm-ppc
and arch/ppc core support. :)

-Matt

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-03 20:48 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
2004-06-03 18:50         ` Tom Rini
2004-06-03 20:19           ` Sylvain Munaut
2004-06-03 20:48             ` Matt Porter [this message]
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=20040603134804.B24468@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tnt@246tnt.com \
    --cc=trini@KERNEL.CRASHING.ORG \
    /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).