On Friday 18 December 2009, Dean Glazeski wrote:
> Right now, I'm specifically calling get_nand_device_by_num or some such.
> Can you suggest a better method or direct me to an example NAND flash? I'm
> not really aware of any other method.
>
> > > +...@deffn Command {at91sam9 ale} num addr_line
Yep, addr_line is a number like "8" that I automatically shift so that I
don't have to specify the line using binary notation. It's just easier to
handle it in C in my opinion.
ALE and CLE do have defaults (21 and 22 respectively). Ready/~Busy and chip
enable do not have defaults, however, but i
Right now, I'm specifically calling get_nand_device_by_num or some such.
Can you suggest a better method or direct me to an example NAND flash? I'm
not really aware of any other method.
// Dean Glazeski
On Fri, Dec 18, 2009 at 4:13 AM, David Brownell wrote:
> On Thursday 17 December 2009, Dea
On Thursday 17 December 2009, Dean Glazeski wrote:
> +...@deffn Command {at91sam9 cle} num addr_line
So "addr_line" is for example "8" to indicate that A8 is
used to drive the CLE signal? Or should that be 0x0100
instead?
And ... are there defaults, or are ALE and CLE "must specify"
things? If
On Thursday 17 December 2009, Dean Glazeski wrote:
> +...@deffn Command {at91sam9 cle} num addr_line
> +Configure the address line used for latching commands. The @var{num}
> +parameter is the value shown by @command{nand list}.
> +...@end deffn
> +...@deffn Command {at91sam9 ale} num addr_line
>
This creates the TCL interface for configuring an AT91SAM9 NAND flash controller
and implements the necessary functions to correctly work with a NAND flash
device connected to the chip. This includes updates to the driver list and the
Makefile.am to support building the driver and also houses the
