linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Roberto Guerra <roberto.j.guerra@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: Support for S29JL064 in MPC8272ADS?
Date: Fri, 9 Oct 2009 13:59:58 -0400	[thread overview]
Message-ID: <7c4144600910091059o492c870cn3ea1c1a96d2f0823@mail.gmail.com> (raw)
In-Reply-To: <20091009170433.GA17372@b07421-ec1.am.freescale.net>

No. I did not. My FDT was simplified from the stock MPC8272ADS:
=> fdt list
/ {
        model = "pq2fads";
        compatible = "fsl,pq2fads";
        #address-cells = <0x00000001>;
        #size-cells = <0x00000001>;
        cpus {
        };
        memory {
        };
        soc@f0000000 {
        };
        chosen {
        };
};
I am searching how I could add the mtd branch between the "soc" and
the "chosen".

On Fri, Oct 9, 2009 at 1:04 PM, Scott Wood <scottwood@freescale.com> wrote:
> On Fri, Oct 09, 2009 at 10:14:56AM -0400, Roberto Guerra wrote:
>> Hello,
>> My uboot can read my flash chip, finding the uImage and the initramfs,
>> and booting the kernel fine. However, I'd like the Linux kernel to
>> read my flash chip so that it can update files in it.
>
> Have you described your flash chip in the device tree?
>
>> However, the kernel does not detect any flash chip (nor there's any
>> indication that a CFI probe is being performed).
>
> The stock device tree for mpc8272ads only specifies it as a JEDEC
> flash, not CFI.
>
> -Scott
>

  reply	other threads:[~2009-10-09 18:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 14:14 Support for S29JL064 in MPC8272ADS? Roberto Guerra
2009-10-09 17:04 ` Scott Wood
2009-10-09 17:59   ` Roberto Guerra [this message]
2009-10-09 18:16     ` Scott Wood
2009-10-14 21:34       ` Roberto Guerra
2009-10-14 21:40         ` Scott Wood
2009-10-16 15:37           ` Roberto Guerra
2009-10-16 15:55             ` Roberto Guerra
2009-10-16 16:18             ` Scott Wood

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=7c4144600910091059o492c870cn3ea1c1a96d2f0823@mail.gmail.com \
    --to=roberto.j.guerra@gmail.com \
    --cc=linuxppc-dev@lists.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).