From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] at91sam9x5ek: Pass serial and revision tags to Linux
Date: Fri, 10 May 2013 09:37:09 +0800 [thread overview]
Message-ID: <518C4F45.2060203@atmel.com> (raw)
In-Reply-To: <CAFHsovenUB6fPBKRcN4Eh6YnnFu4pKtPtbB6J9Pb_M4NdUC36Q@mail.gmail.com>
Hi Julius,
On 5/10/2013 01:07, Julius Hemanth P wrote:
> This code is small snippet from patch
> ftp://ftp.linux4sam.org/pub/uboot/u-boot-v2010.06/u-boot-5series_1.0.patch
>
> Linux 2.6.39 (released on www.at91.com/linux4sam) requires serial and
> revision ATAGs to detect NAND device.
>
> This patch provides backward compatibility for old Linux 2.6.39 by
> passing serial and revision ATAGs to Linux kernel.
>
> Signed-off-by: Julius Hemanth <juliushemanth@gmail.com>
> ---
> Changes for v3:
> - corrected GPBR register access
> - updated commit message
>
> Changes for v2:
> - access GPBR using c structure
> - removed tailing 1 for #define
> - s/Miscelaneous/Miscellaneous
> - s/initialisations/initializations
>
> board/atmel/at91sam9x5ek/at91sam9x5ek.c | 33 ++++++++++++++++++++++++++++++++-
> include/configs/at91sam9x5ek.h | 5 +++++
> 2 files changed, 37 insertions(+), 1 deletion(-)
Sorry for forgetting to mention check your patch before you send it.
please use ./tools/checkpatch.pl under u-boot to check your patch.
Best Regards,
Bo Shen
next prev parent reply other threads:[~2013-05-10 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 17:07 [U-Boot] [PATCH v3] at91sam9x5ek: Pass serial and revision tags to Linux Julius Hemanth P
2013-05-10 1:37 ` Bo Shen [this message]
2013-05-10 6:51 ` Andreas Bießmann
2013-05-10 11:40 ` Julius Hemanth P
2013-05-10 13:38 ` Andreas Bießmann
2013-05-11 5:01 ` Julius Hemanth P
2013-05-13 2:39 ` Bo Shen
2013-05-13 14:30 ` Julius Hemanth P
-- strict thread matches above, loose matches on Subject: below --
2013-05-09 16:58 [U-Boot] [PATCH v3] at91sam9x5ek:Pass " Julius Hemanth P
2013-05-09 17:11 ` Julius Hemanth P
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=518C4F45.2060203@atmel.com \
--to=voice.shen@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox