From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] Revert "i.MX28: Enable additional DRAM address bits"
Date: Thu, 3 May 2012 15:36:53 +0200 [thread overview]
Message-ID: <201205031536.53380.marex@denx.de> (raw)
In-Reply-To: <m2d36lsmz0.fsf@lamuella.denx.de>
Dear Detlev Zundel,
> Hi Marek,
>
> > This reverts commit 69d26d09de1cb93e0a09ca71d9f0d41a66f0756a.
> >
> > Apparently, this commit got mainline only because of OOT port and causes
> > breakage on board that is mainline. Revert.
>
> To be honest, I don't understand what this patch or what the original
> patch did, nor through what OOT port this hit mainline and what breakage
> it causes on other boards.
It enabled some additional address bits on X board, allowing it to use full
512MB of RAM. But because we don't have any other such configured board and X
board isn't mainline, I reverted this patch. It caused trouble on new 256MB
configuration of M28.
Once there'll be some module that needs different memory configuration (like X
board) mainline, we'll add this here, but until then, I'd like to stick with
common memory init.
>
> So also I can read the sentence, I cannot make heads and tails of it.
> Can you please write commit messages that people like me can make some
> sense from? I.e. answering the following questions would help me
>
> - What does the original commit do? (its too late to change the original
> commit)
Enabled additional address bits, to address full 512 MB of DRAM on the X board.
> - Why was the change made in the first place and for what OOT port?
Change of a DRAM configuration register that enabled additional address bit, at
address 512MB of DRAM. Though this caused memory hole on our M28 module with
256MB of DRAM, which _is_ mainline. X board is OOT and never will be mainlined I
guess.
> - What breakage is caused on what boards?
See above.
> - Why can we revert the change without any problems?
Because we don't have any mainline port that used this feature.
>
> Thanks
> Detlev
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-05-03 13:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 22:14 [U-Boot] [PATCH 1/3] Revert "i.MX28: Enable additional DRAM address bits" Marek Vasut
2012-05-02 22:14 ` [U-Boot] [PATCH 2/3] M28: Scan only first 512 MB of DRAM to avoid memory wraparound Marek Vasut
2012-05-02 22:14 ` [U-Boot] [PATCH 3/3] i.MX28: Increase the delay after DRAM init Marek Vasut
2012-05-02 22:55 ` Fabio Estevam
2012-05-02 23:27 ` Marek Vasut
2012-05-03 8:12 ` Detlev Zundel
2012-05-03 13:31 ` Marek Vasut
2012-05-03 14:27 ` Detlev Zundel
2012-05-03 14:39 ` Marek Vasut
2012-05-03 15:34 ` Marek Vasut
2012-05-04 9:16 ` Detlev Zundel
2012-05-03 8:11 ` [U-Boot] [PATCH 1/3] Revert "i.MX28: Enable additional DRAM address bits" Detlev Zundel
2012-05-03 13:36 ` Marek Vasut [this message]
2012-05-03 14:30 ` Detlev Zundel
2012-05-03 14:41 ` Marek Vasut
2012-05-04 9:15 ` Detlev Zundel
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=201205031536.53380.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.