From: "Dale Farnsworth" <dale@farnsworth.org>
To: Wolfgang Denk <wd@denx.de>, linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC5200 Patches
Date: Sun, 16 Nov 2003 23:07:01 -0700 [thread overview]
Message-ID: <20031117060701.GA26252@zenos.farnsworth.org> (raw)
In-Reply-To: <20031116203318.21D9CC5F59@atlas.denx.de>
On Sun, Nov 16, 2003 at 08:33:13PM +0000, Wolfgang Denk wrote:
> Dear Tom & Dale,
>
> OK, so the discussion has stopped. What's happening now? I sent our
> stuff. Dale has added some modification. We have more works in the
> queue. I think it makes little sense to continue without a common
> code base.
>
> Can you give any estimates when something will go into a public tree,
> and what this will be, and which tree?
>
> If there is any reason for you not to use the "common" trees (like
> linuxppc_2_4_devel ?) yet, maybe we can at least put the current
> state into a more dedicated tree like
> bk://source.mvista.com/linuxppc_2_4_mgt5100
>
> So that we can at least avoid to duplicate efforts while the work is
> going on?
Hi Wolfgang,
Have you had a chance to test my merged patch? Any bug fixes? I don't
think it's quite ready for linuxppc_2_4_devel, though it's close.
Per your suggestion above, I created
bk://source.mvista.com/linuxppc_2_4_mpc5200
It incorporates my merged patch with the following changes from the
discussion in this thread:
o s/CONFIG_5XXX/CONFIG_PPC_5xxx/
o s/i2c-algo-m5xxx.c/i2c-algo-ppc_5xxx.c/
o s/UBoot/U-Boot/
o s/M?5[xX][xX][xX]/MPC5xxx/
o s/m?5[xX][xX][xX]/mpc5xxx/
o changed default CONFIG_MPC5xxx_FLASH_SIZE to 0x1000000
I think the name changes are a definite improvement. Thanks to all
for the input.
Please try this new tree and submit patches against it.
Thank you,
-Dale Farnsworth
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-17 6:07 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 [this message]
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
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=20031117060701.GA26252@zenos.farnsworth.org \
--to=dale@farnsworth.org \
--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).