mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: add pxa3xx-nand driver
Date: Mon, 05 Jan 2015 21:32:32 +0100	[thread overview]
Message-ID: <874ms555pb.fsf@free.fr> (raw)
In-Reply-To: <20150105120322.GB4544@pengutronix.de> (Sascha Hauer's message of "Mon, 5 Jan 2015 13:03:22 +0100")

Sascha Hauer <s.hauer@pengutronix.de> writes:

> Hi Robert,
>
> Things like mtd->writesize, mtd->erasesize, and mtd->size should be
> initialized after calling nand_scan_ident(). These are currently
> overwritten by the pxa nand driver, but normally you should be able to
> remove this.
You're right, the extended id parsing should take care of that.

> IIRC barebox can also detect the chip widths automatically.
Yup, that's also in the extended id parsing.

> I don't know how to get the timings though.
I have an idea here : as barebox is not performance oriented, and as the timings
are minimum guaranteed times between signal swaps, let me try to hard encode all
timing with their maximum value.

Of course performance will suffer, but as long it remains usable with a loss of
20% or less in throughput, that will be a cool simplification.

Cheers.

-- 
Robert

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2015-01-05 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 21:58 Robert Jarzmik
2015-01-04 18:50 ` Ezequiel Garcia
2015-01-05 10:44   ` robert.jarzmik
2015-01-05 12:03     ` Sascha Hauer
2015-01-05 20:32       ` Robert Jarzmik [this message]
2015-01-05 20:33         ` Ezequiel Garcia
2015-01-05 22:42           ` Robert Jarzmik

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=874ms555pb.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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