From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/6] README: mx28_common: Do not hardcode the SSP port
Date: Fri, 3 May 2013 22:47:21 +0200 [thread overview]
Message-ID: <201305032247.21397.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5DBuu+d8PQ_EpeLYn_YwWtPE-u++h9_kQUYZXcWiVHx3A@mail.gmail.com>
Dear Fabio Estevam,
> On Fri, May 3, 2013 at 4:52 PM, Marek Vasut <marex@denx.de> wrote:
> >> To boot a MX28 based board from SD, set the boot mode DIP switches
> >>
> >> according -to i.MX28 manual chapter 12.2.1 (Table 12-2), PORT=SSP0,
> >> SD/MMC master on -SSP0, 3.3V.
> >> -
> >> +to i.MX28 manual chapter 12.2.1 (Table 12-2).
> >
> > Make sure to leave the 3V3 thing there. PORT=SSPn would be a better
> > solution here too.
>
> Sorry, but I disagree.
>
> Please check table 12-2 from mx28 reference manual and you will see
> that SD boot is also possible in 1.8V, so in the common README file it
> makes no sense to hardcode the boot voltage. Besides that, mx23 does
> not refer to 3.3V in its boot mode table.
When was the last time you saw 1V8 SD card ? ;-)
> PORT=SSPn is also noisy. Let's get rid of all this. People will have
> to look the reference manual anyway.
>
> Also, in v2 I will change "set the boot mode DIP switches" to "set the
> boot mode pins", as not all boards use DIP switches.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-05-03 20:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 18:07 [U-Boot] [PATCH 1/6] README: mx28_common: Keep the text within 80 columns Fabio Estevam
2013-05-03 18:07 ` [U-Boot] [PATCH 2/6] README: mx28_common: Do not hardcode the SSP port Fabio Estevam
2013-05-03 19:52 ` Marek Vasut
2013-05-03 20:42 ` Fabio Estevam
2013-05-03 20:47 ` Marek Vasut [this message]
2013-06-26 15:42 ` Stefano Babic
2013-05-03 18:07 ` [U-Boot] [PATCH 3/6] README: mx28_common: Fix structure of sentence Fabio Estevam
2013-06-26 15:42 ` Stefano Babic
2013-05-03 18:08 ` [U-Boot] [PATCH 4/6] README: mxs: Introduce README.mxs Fabio Estevam
2013-05-03 19:54 ` Marek Vasut
2013-06-26 15:42 ` Stefano Babic
2013-05-03 18:08 ` [U-Boot] [PATCH 5/6] mx28evk: Move README file inside board directory Fabio Estevam
2013-06-26 15:43 ` Stefano Babic
2013-06-26 15:46 ` Otavio Salvador
2013-06-26 19:57 ` Marek Vasut
2013-05-03 18:08 ` [U-Boot] [PATCH 6/6] m28evk: " Fabio Estevam
2013-05-03 19:54 ` Marek Vasut
2013-05-03 20:23 ` Fabio Estevam
2013-05-03 20:47 ` Marek Vasut
2013-06-26 15:44 ` Stefano Babic
2013-06-26 15:43 ` [U-Boot] [PATCH 1/6] README: mx28_common: Keep the text within 80 columns Stefano Babic
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=201305032247.21397.marex@denx.de \
--to=marex@denx.de \
--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.