linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
Cc: Kumar Gala <kumar.gala@motorola.com>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Proposed Kconfig update patch for help text)
Date: Thu, 1 Apr 2004 10:19:56 -0700	[thread overview]
Message-ID: <20040401171956.GD26876@smtp.west.cox.net> (raw)
In-Reply-To: <20040401170515.E5C8EC10A4@atlas.denx.de>


On Thu, Apr 01, 2004 at 07:05:10PM +0200, Wolfgang Denk wrote:
> In message <20040401161622.GA26876@smtp.west.cox.net> you 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, from it's
> > buggy to it being unacceptable crap.  Finally, 2.4 is about to enter a
>
> So far, it's all we have, right? Or do you have anything significant-
> ly better?

As I said, someone is working on the second option I described, but I
don't know how far they have gotten.

> > "deep freeze", or so Marcelo intends at least, so I think it's out of
> > the question for the mainline.  I don't mind keeping the
>
> So why made you me submit all the stuff in the first place  when  you
> were going to put it on hold until it was too late for inclusion?

When I asked, there was time.  Once I started trying to get people to
review it (since that's what upstream people like, and it's good
practice) it became apparent that the code wasn't in good enough shape
to get in.

> > For 2.6, I think one of the following options needs to be done.
> > - Motorola code, cleaned up with input from the community (and the bits
> >   Linux just doesn't need, left out).
>
> I think this is the only option there is.
>
> > - Ignore the Motorola code, or since it's GPL (must be to be in the
> >   kernel, so I'm just making the assumption here...) use it as a guide
> >   for how things work to implement a clean Linux implementation of the
> >   code.   I know there's someone working on this (who pops up on
> >   #mklinux on freenode from time to time) but I don't know how far
> >   they've gotten.
>
> Ummm... Why is there no discussion about this on  any  mailing  list?

There was some discussion in the same thread where people like benh
pointed out how bad the code is.  And there's a discussion right now,
right here even.

> And don't you think that that at least Motorola should be included in
> any  such  attempts? [AFAICT they are not, at least not until today.]

Well, Kumar is cc'ed here, and he's even on #mklinux on freenode where
Paul, benh, myself, and a lot of other people (including the person who
I suspect is on this list, but I don't know) who're working on 5xxx for
2.6 support, without the Motorola code.  If there's a specific person at
Motorola who'd be interested in what the Linux community has to say
about the DMA code, no one has told me who.

> Also, isn't this kind of wasted effort as the target is still moving?

What target?  The Motorola code?  The 5xxx hw line?  If you're talking
about kernels, the only non-moving target right now is 2.2, but I don't
think you're talking about that.

--
Tom Rini
http://gate.crashing.org/~trini/

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

  reply	other threads:[~2004-04-01 17:19 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
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 [this message]
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=20040401171956.GD26876@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=kumar.gala@motorola.com \
    --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).