linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add support for the MPC8349E-mITX-GP
Date: Fri, 26 Jan 2007 09:08:02 -0600	[thread overview]
Message-ID: <45BA1952.80206@freescale.com> (raw)
In-Reply-To: <309FC1DE-9724-4172-BB13-D301D4A783F8@kernel.crashing.org>

Kumar Gala wrote:
> 
> On Jan 18, 2007, at 3:33 PM, Timur Tabi wrote:
> 
>> Adds support for the MPC8349E-mITX-GP, which is a stripped-down version
>> of the MPC8349E-mITX reference board from Freescale.
>>
>> Signed-off-by: Timur Tabi <timur@freescale.com>
>> ---
>>  arch/powerpc/boot/dts/mpc8349emitx-gp.dts     |  190 ++++
>>  arch/powerpc/configs/mpc834x_itx_gp_defconfig | 1422 
>> +++++++++++++++++++++++++
>>  2 files changed, 1612 insertions(+), 0 deletions(-)
> 
> Why does the defconfig differ so much from the mpc834x_itx_defconfig?

I just did a "make mpc834x_itx_defconfig" and used "make menuconfig" to change a 
couple options, then did a save.  My guess is that when menuconfig rewrote the 
file, it made major changes, including new defaults for the 2.6.19-whatever kernel.

Was I supposed to hand-edit the config file to make the minimum number of changes?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-01-26 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 21:33 [PATCH] Add support for the MPC8349E-mITX-GP Timur Tabi
2007-01-26  6:19 ` Kumar Gala
2007-01-26 15:08   ` Timur Tabi [this message]
2007-01-26 15:22     ` Kumar Gala
2007-01-29 16:36       ` Timur Tabi
2007-01-29 16:37         ` Kumar Gala
2007-01-29 19:32           ` Timur Tabi
2007-01-29 19:55             ` Kumar Gala
2007-01-29 23:15             ` Paul Mackerras

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=45BA1952.80206@freescale.com \
    --to=timur@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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).