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>,
Sylvain Munaut <tnt@246tNt.com>
Subject: Re: Proposed Kconfig update patch for help text)
Date: Thu, 1 Apr 2004 12:11:31 -0700 [thread overview]
Message-ID: <20040401191131.GG26876@smtp.west.cox.net> (raw)
In-Reply-To: <20040401185656.871ECC10A4@atlas.denx.de>
On Thu, Apr 01, 2004 at 08:56:51PM +0200, Wolfgang Denk wrote:
> In message <20040401171956.GD26876@smtp.west.cox.net> you wrote:
> >
> > > 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.
>
> Is this a secret or what? Why don't you give names? Why doesn't he
> show up on this list?
Because I'm not omniscient? Looking back in the linuxppc-embedded
archives, and recalling his nickname from IRC, it appears to be Sylvain
Munaut <tnt@246tNt.com>, whom you've even answered 5200 questions for.
Sylvain, have you made much progress on 52xx support in 2.6?
> > 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.
>
> You are not working on this, or are you?
<hat="MontaVista Employee">I personally am not, but I know engineers
who are or have in the recent past, worked on 5xxx && Linux in MV</hat>
<hat="Community Person">Since I do try and get changes people make into
kernel.org, Yes</hat>
> > > 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
>
> The Motorola code, and to some extend the hardware.
As I've stated before, in reference to other vendor-provided HAL code,
if the vendor is willing to work to address community concerns about the
vendor code (which includes subscribing to linuxppc-dev and -embedded so
they can field questions / comments / concerns about it), that works for
me. But I had been under the impression that Motorola did not
particularly care to fix the concerns that had been raised. If this
impression is incorrect, then I'd like to see someone step up, who has
authority to address said concerns (such as to paraphrase Dan Malek, why
do we need this?).
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-01 19:11 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
2004-04-01 18:56 ` Wolfgang Denk
2004-04-01 19:11 ` Tom Rini [this message]
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=20040401191131.GG26876@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=kumar.gala@motorola.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tnt@246tNt.com \
--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).