public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Laxmikant Rashinkar <lk.atwork@yahoo•com>
To: linuxppc-embedded@ozlabs•org
Subject: How to access Freesale UPM NAND device
Date: Wed, 27 Aug 2008 11:16:11 -0700 (PDT)	[thread overview]
Message-ID: <765252.68184.qm@web46305.mail.sp1.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

Hi,

quick question:

I have a custom board running MPC8347 on Linux 2.6.27 with Uboot 1.1.4.
I also have a NAND device (Micron MT29F2G08AACWP) connected to the LBC
and controlled via UPM.

fsl_elbc_nand.ko, fsl_upm.ko are loaded.

I'm wondering how to access the NAND device. Do I need mDOC? TrueFFS?

I have grep'd for the functions declared in fsl_upm.c and fsl_lbc.c and find that no other
code path calls these functions. So it looks like the drivers are loaded but no one calls into
them.

any help appreciated.

thanks
LK


      

[-- Attachment #2: Type: text/html, Size: 798 bytes --]

             reply	other threads:[~2008-08-27 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 18:16 Laxmikant Rashinkar [this message]
2008-08-28 18:57 ` How to access Freesale UPM NAND device 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=765252.68184.qm@web46305.mail.sp1.yahoo.com \
    --to=lk.atwork@yahoo$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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