linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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 15:18:26 -0500	[thread overview]
Message-ID: <4A525C12.3090804@freescale.com> (raw)
In-Reply-To: <4A525B4C.5050600@freescale.com>

Scott Wood wrote:
> Mikhail Zaturenskiy wrote:
>>>> +       CONFIG_BLK_DEV = y
>>> Hmm, missed this.  I'm not sure why the subsequent changes didn't take
>>> effect -- what did the .config look like after sucking in the defconfig
>>> changes, but without any Kconfig changes?
>>
>> I reverted back all the Kconfig changes and made the changes just in
>> ep88xc_defconfig. See attached files for details, (didn't want a
>> mile-long email).
>>
>> Does this tell you anything?
> 
> CONFIG_BLK_DEV is enabled in that output.  That was the only change that 
> I saw you make to the config in the previous e-mail -- no 
> CONFIG_BLK_DEV_RAM, etc:
> 
>> ****************************************************
>> 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

OK, looked at the attached defconfig (didn't notice that until after I 
hit send).

Try omitting the spaces around the equal sign.  BLK_DEV likely worked 
because it's default y and because you removed the "is not set" line, 
not because you added the = y line.

-Scott

  reply	other threads:[~2009-07-06 20:18 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
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 [this message]
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=4A525C12.3090804@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).