Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: Quad Die NAND Chip with 16Gb
Date: Fri, 31 Aug 2007 17:31:32 +0200	[thread overview]
Message-ID: <20070831153132.GA27851@z1.synertronixx> (raw)
In-Reply-To: <20070831150443.GA10808@anita.doom>

Replying to myself *mumblegrumble*

I am trying to picture of NAND code and tried this: Why can't I access
the one or the other half of the device?

Platform Setup:

static struct scb9xxx_nand_pdata __initdata nand_pdata = {
        .ce1            = CPLD_NAND_CE2,
        .ale            = CPLD_NAND_ALE,
        .cle            = CPLD_NAND_CLE,
        .rdy            = CPLD_NAND_RYBY,
        .partition_info = nand_partitions,
};

For .ce1 I put CPLD_NAND_CE1 or CPLD_NAND_CE2 and booting yields in seeing
the one or the other half of the device. 
Hardware feels well, so how does stupid konste merge these halfes?
Or could they be accessed as two different mtdblockX as an alternative?

Konsti


-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

  reply	other threads:[~2007-08-31 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 15:04 Quad Die NAND Chip with 16Gb Konstantin Kletschke
2007-08-31 15:31 ` Konstantin Kletschke [this message]
2007-09-04 10:32   ` Konstantin Kletschke

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=20070831153132.GA27851@z1.synertronixx \
    --to=lists@ku-gbr.de \
    --cc=linux-mtd@lists.infradead.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