linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Wolfgang Denk <wd@denx.de>, Kumar Gala <kumar.gala@motorola.com>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: mpc5xxx support (Was: Re: Proposed Kconfig update patch for help text)
Date: Thu, 01 Apr 2004 11:58:14 -0500	[thread overview]
Message-ID: <406C4A26.3040107@embeddededge.com> (raw)
In-Reply-To: 20040401161622.GA26876@smtp.west.cox.net


Tom Rini wrote:

> In all seriousness, when the 52xx code for 2.4 was brought up, there
> were a number of objections to the Motorola provided code,

Does anyone actually use this code?  From the work I've done it appears
the FEC implements it's own DMA, other peripherals are used in programmed I/O
mode, and stuff I have done I've found it easier to just write my own
code manage the DMA.  IMHO we should just punt this stuff for Linux,
now that there is more public interest start collaborating on a better
solution, and maybe just use what Mot provided as documentation filler.
The Motorola solution seems like an attempt to be everything for everyone.

Thanks.


	-- Dan


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

  reply	other threads:[~2004-04-01 16:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31 22:42 Proposed Kconfig update patch for help text John Whitney
2004-03-31 23:06 ` Wolfgang Denk
2004-04-01  0:04   ` Dan Malek
2004-04-01  0:14   ` John Whitney
2004-04-01  8:35     ` Geert Uytterhoeven
2004-04-01 13:49       ` Kumar Gala
2004-04-01 15:02         ` Wolfgang Denk
2004-04-01 16:16           ` mpc5xxx support (Was: Re: Proposed Kconfig update patch for help text) Tom Rini
2004-04-01 16:58             ` Dan Malek [this message]
2004-04-01 17:03               ` Tom Rini
2004-04-01 17:18               ` mpc5xxx support (Was: " Wolfgang Denk
2004-04-01 17:05             ` Wolfgang Denk
2004-04-01 17:19               ` Tom Rini
2004-04-01 18:56                 ` Wolfgang Denk
2004-04-01 19:11                   ` Tom Rini
2004-04-02  0:24               ` mpc5xxx support (Was: " Sylvain Munaut
2004-04-01 23:35             ` Sylvain Munaut
2004-04-02  2:59               ` New OCP for 2.6 was (Re: mpc5xxx support ) Matt Porter
2004-04-02 16:56               ` mpc5xxx support (Was: Re: Proposed Kconfig update patch for help text) Wolfgang Denk
2004-04-02 17:21                 ` Sylvain Munaut
2004-04-07 14:00                   ` Wolfgang Denk
2004-04-07 14:16                     ` Sylvain Munaut
2004-04-01 15:26         ` Proposed Kconfig update patch for help text Tom Rini
2004-04-01 21:50       ` John Whitney
2004-04-07 14:25         ` Kumar Gala
2004-04-07 15:01         ` Kumar Gala

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=406C4A26.3040107@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=kumar.gala@motorola.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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).