From: Scott Wood <scottwood@freescale.com>
To: Mikhail Zaturenskiy <mzaturenskiy.st@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: RAMDISK on EP88xc
Date: Mon, 06 Jul 2009 13:57:50 -0500 [thread overview]
Message-ID: <4A52492E.1020707@freescale.com> (raw)
In-Reply-To: <97dd5fd20907061150o303418a3m3967650433fbb061@mail.gmail.com>
Mikhail Zaturenskiy wrote:
>>> 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
You should definitely not do that. In fact, I'm surprised kconfig
didn't complain about the duplicate symbols.
Perhaps CONFIG_BLK_DEV is unset?
-Scott
next prev parent reply other threads:[~2009-07-06 18:57 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
2009-07-06 18:57 ` Scott Wood [this message]
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=4A52492E.1020707@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mzaturenskiy.st@gmail.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).