From: Christoph Hellwig <hch@lst.de>
To: Wolfgang Denk <wd@denx.de>
Cc: Christoph Hellwig <hch@lst.de>,
Tom Rini <trini@kernel.crashing.org>,
Dale Farnsworth <dale@farnsworth.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC5200 Patches
Date: Thu, 20 Nov 2003 13:17:17 +0100 [thread overview]
Message-ID: <20031120121717.GA7764@lst.de> (raw)
In-Reply-To: <20031120121037.90F93C5F5F@atlas.denx.de>
On Thu, Nov 20, 2003 at 01:10:32PM +0100, Wolfgang Denk wrote:
> In message <20031120115315.GA7411@lst.de> you wrote:
> >
> > Umm, the code needs a rewrite before it's suitable for mainline. In
>
> Are you volunteering? ;-)
Sure, feel free to contract me for that.
> > it's current state is just bogus utter crap. The bestcomm API needs
> > to go away and the dma engine used directly.
>
> It would be nice if you explained your reasons for such a statement.
Because Linux is about doing things right, not fast? Look at the bogus
taks abstractions - you just call into some deep multiplexer calls to
load pregenerated and (accoring to benh who worked with the even more
buggy predessecor) often bogus. It looks like MOT once again produced
a really crappy chip and now hides the interface behind a huge bloated
API. That might be find for them to sell the POS to someone wearing
Suits, but it's not really enough to get it included into the kernel
tree.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-20 12:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 9:36 MPC5200 Patches Wolfgang Denk
2003-11-03 23:31 ` Dale Farnsworth
2003-11-07 22:20 ` Wolfgang Denk
2003-11-10 19:02 ` Dale Farnsworth
2003-11-10 20:46 ` Wolfgang Denk
2003-11-10 21:00 ` Tom Rini
2003-11-12 0:34 ` Wolfgang Denk
2003-11-12 4:50 ` Dale Farnsworth
2003-11-12 9:30 ` Geert Uytterhoeven
2003-11-12 9:49 ` Wolfgang Denk
2003-11-12 9:59 ` Geert Uytterhoeven
2003-11-12 11:41 ` Gabriel Paubert
2003-11-12 11:51 ` Geert Uytterhoeven
2003-11-12 14:47 ` Wolfgang Denk
2003-11-12 14:45 ` Wolfgang Denk
2003-11-12 17:43 ` Gabriel Paubert
2003-11-12 19:41 ` Geert Uytterhoeven
2003-11-14 6:11 ` Kumar Gala
2003-11-14 15:20 ` Tom Rini
2003-11-12 15:18 ` Tom Rini
2003-11-12 15:49 ` Gary Thomas
2003-11-12 15:53 ` Tom Rini
2003-11-16 20:33 ` Wolfgang Denk
2003-11-17 6:07 ` Dale Farnsworth
2003-11-17 8:35 ` Wolfgang Denk
2003-11-17 15:19 ` Tom Rini
2003-11-17 16:02 ` Wolfgang Denk
2003-11-17 16:25 ` Tom Rini
2003-11-18 14:52 ` Dale Farnsworth
2003-11-20 11:53 ` Christoph Hellwig
2003-11-20 12:10 ` Wolfgang Denk
2003-11-20 12:17 ` Christoph Hellwig [this message]
2003-11-21 1:04 ` Paul Mackerras
2003-11-18 0:43 ` Benjamin Herrenschmidt
2003-11-18 0:44 ` Benjamin Herrenschmidt
2003-11-18 14:45 ` Wolfgang Denk
2003-11-18 15:00 ` Wolfgang Denk
2003-11-17 18:50 ` Tom Rini
2003-12-03 18:28 ` Dale Farnsworth
[not found] ` <20031203185310.19A48C5F5F@atlas.denx.de>
2003-12-04 0:35 ` Dale Farnsworth
[not found] ` <20031110162536.GC8584@ip68-0-152-218.tc.ph.cox.net>
2003-11-10 19:09 ` Dale Farnsworth
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=20031120121717.GA7764@lst.de \
--to=hch@lst.de \
--cc=dale@farnsworth.org \
--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).