From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OneNAND: Destaticize largepage_memorybased
Date: Sat, 2 Oct 2010 16:35:19 +0200 [thread overview]
Message-ID: <201010021635.19270.marek.vasut@gmail.com> (raw)
In-Reply-To: <1286029567-30231-1-git-send-email-marek.vasut@gmail.com>
Dne So 2. ??jna 2010 16:26:07 Marek Vasut napsal(a):
> This moves "struct nand_bbt_descr largepage_memorybased" into .data.rel,
> which allows it to be PIC with current U-Boot infrastructure for
> relocation.
>
> Also, I squished the ff_patternt into the structure.
Please ignore this one, the linker is playing weird games with me ...
>
> Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
> ---
> drivers/mtd/onenand/onenand_bbt.c | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mtd/onenand/onenand_bbt.c
> b/drivers/mtd/onenand/onenand_bbt.c index 1354877..c6d1dc9 100644
> --- a/drivers/mtd/onenand/onenand_bbt.c
> +++ b/drivers/mtd/onenand/onenand_bbt.c
> @@ -231,13 +231,11 @@ int onenand_scan_bbt(struct mtd_info *mtd, struct
> nand_bbt_descr *bd) * Define some generic bad / good block scan pattern
> which are used * while scanning a device for factory marked good / bad
> blocks.
> */
> -static uint8_t scan_ff_pattern[] = { 0xff, 0xff };
> -
> -static struct nand_bbt_descr largepage_memorybased = {
> +struct nand_bbt_descr largepage_memorybased = {
> .options = 0,
> .offs = 0,
> .len = 2,
> - .pattern = scan_ff_pattern,
> + .pattern = { 0xff, 0xff },
> };
>
> /**
next prev parent reply other threads:[~2010-10-02 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 14:26 [U-Boot] [PATCH] OneNAND: Destaticize largepage_memorybased Marek Vasut
2010-10-02 14:35 ` Marek Vasut [this message]
2010-10-03 18:10 ` Wolfgang Denk
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=201010021635.19270.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.