From: Mikhail Zaturenskiy <mzaturenskiy.st@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: RAMDISK on EP88xc
Date: Mon, 6 Jul 2009 13:50:08 -0500 [thread overview]
Message-ID: <97dd5fd20907061150o303418a3m3967650433fbb061@mail.gmail.com> (raw)
In-Reply-To: <4A5244B6.7030800@freescale.com>
>> After doing this testing I have a side question:
>> If I modify just arch/powerpc/configs/ep88x_defconfig, not all changes
>> are reflected in the resulting .config when i do "make
>> ep88x_defconfig; make uImage". I ended up having to modify
>> arch/powerpc/Kconfig, arch/powerpc/configs/ep88xc_defconfig,
>> fs/ext2/Kconfig and init/Kconfig to get "make ep88x_defconfig; make
>> uImage" to create a properly configured image, but this really doesn't
>> feel right. What's the proper way to set up a defconfig?
>
> What changes are you trying to make to the config, and what did you change
> in the Kconfig files?
>
****************************************************
in arch/powerpc/Kconfig:
+ config BLK_DEV_LOOP
+ tristate
+ default y
+ config BLK_DEV_RAM
+ tristate
+ default y
+ config BLK_DEV_RAM_COUNT
+ int
+ default 16
+ config BLK_DEV_RAM_SIZE
+ int
+ default 32768
****************************************************
in arch/powerpc/configs/ep88xc_defconfig:
+ CONFIG_BLK_DEV = y
- CONFIG_BLK_DEV is not set
- CONFIG_BLK_DEV_INITRD is not set
- CONFIG_EXT2_FS is not set
****************************************************
in fs/ext2/Kconfig/"config EXT2_FS":
+ default y
****************************************************
in init/Kconfig/"config BLK_DEV_INITRD":
+ default y
****************************************************
If I make changes just to arch/powerpc/configs/ep88xc_defconfig they
don't seem to be propagated to the resulting configuration when using
"make ep88xc_defconfig"
next prev parent reply other threads:[~2009-07-06 18:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 18:04 RAMDISK on EP88xc Mikhail Zaturenskiy
2009-07-01 19:52 ` Frank Svendsbøe
2009-07-01 20:14 ` Mikhail Zaturenskiy
2009-07-02 7:10 ` Frank Svendsbøe
2009-07-02 13:43 ` Mikhail Zaturenskiy
2009-07-02 13:54 ` Gary Thomas
2009-07-02 16:27 ` Mikhail Zaturenskiy
2009-07-02 18:42 ` Mikhail Zaturenskiy
2009-07-02 19:11 ` Mikhail Zaturenskiy
2009-07-02 20:38 ` Frank Svendsbøe
2009-07-02 21:38 ` Mikhail Zaturenskiy
2009-07-02 21:49 ` Scott Wood
2009-07-02 21:57 ` Mikhail Zaturenskiy
2009-07-06 18:29 ` Mikhail Zaturenskiy
2009-07-06 18:38 ` Scott Wood
2009-07-06 18:50 ` Mikhail Zaturenskiy [this message]
2009-07-06 18:57 ` Scott Wood
2009-07-06 19:01 ` Scott Wood
2009-07-06 19:28 ` Mikhail Zaturenskiy
2009-07-06 20:15 ` Scott Wood
2009-07-06 20:18 ` Scott Wood
2009-07-06 20:26 ` Mikhail Zaturenskiy
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=97dd5fd20907061150o303418a3m3967650433fbb061@mail.gmail.com \
--to=mzaturenskiy.st@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
/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).