From: Nick Thompson <nick.thompson@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] da830: disable cache usage due to coherency issues
Date: Wed, 14 Sep 2011 12:07:26 +0100 [thread overview]
Message-ID: <4E708AEE.4050508@ge.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593025750A0A3@dbde02.ent.ti.com>
On 14/09/11 06:54, Netagunte, Nagabhushana wrote:
> Nick,
>
> I am seeing this issue on da830/da850/dm36x/dm644x.
Strange that I have seen no issue with da830 (OMAP-L137 v1.0 & v1.1 - don't have any v2.0 yet) when tftp'ing the kernel. I do get very occasional errors, but have put this down to network packet loss.
The v1.0 and v1.1 parts do have a d-cache errata, so we only get to use the d-cache in write through mode. This would mean that TCP packet data writes by the processor would never have a coherency problem. Reads could still have an issue, but I think the explanation provided so far referred to TCP packet sending...?
This vintage of da830 will always have to use write trough mode, so there should be no issue...?
> I agree that u-boot will be faster with cache enabled. And also, TI wants it to be enabled soon. Since so many patches are lined u, we don't up-streaming them to get hampered because of this issue. So, we are trying to push this
> Patch. We are committed come up with appropriate patch to fix the EMAC and coherency issue.
>
> Meanwhile, we are trying to gather info about earlier patch/changes which disabled cache so that community understands the known issue.
Boot time is critical to us. I can't ship without cache enabled. I can use my own _config.h of course to work around it I think, but I don't understand why you think there is an issue to fix on da830 yet. With a working d-cache I can imagine such a problem though.
> Also, one more engineer observed the issue with EMAC, I will send his mail to you.
>
> Regards,
> Nag
> On Wed, Aug 31, 2011 at 15:09:35, Nick Thompson wrote:
>> On 31/08/11 06:40, Netagunte, Nagabhushana wrote:
>>> Mike,
>>>
>>> We will address cache coherency issues soon after these patches.
>>> Earlier also, chache was disabled. Only due to new cache management Framework which was added recently, it is explicitly needed to be indicated to turn off cache.
>>>
>>> Since fixing the cache coherency issues with EMAC will take some time, I want this patch to go in mainline so that issue doesn't crop up for People who use u-boot.
>>>
>>> Regards,
>>> Nag
>>>
>> Which device(s) does this occur on? I have a lot of OMAP-L137 (EVM and custom) boards with cache enabled and no problems tftp'ing the kernel.
>>
>> On the other hand tftp and kernel CRC checking are much faster with cache enabled.
>>
>> Nick.
>>
next prev parent reply other threads:[~2011-09-14 11:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 12:15 [U-Boot] [PATCH 0/5] feature additions and fixes for da830 nagabhushana.netagunte at ti.com
2011-08-30 12:15 ` [U-Boot] [PATCH 1/5] da830: disable cache usage due to coherency issues nagabhushana.netagunte at ti.com
2011-08-30 15:15 ` Mike Frysinger
2011-08-31 5:40 ` Netagunte, Nagabhushana
2011-08-31 9:39 ` Nick Thompson
2011-09-14 5:54 ` Netagunte, Nagabhushana
2011-09-14 11:07 ` Nick Thompson [this message]
2011-09-14 14:05 ` Tom Rini
2011-09-14 14:17 ` Netagunte, Nagabhushana
2011-08-31 14:35 ` Mike Frysinger
2011-08-30 12:15 ` [U-Boot] [PATCH 2/5] da830: enable SPI flash boot mode nagabhushana.netagunte at ti.com
2011-08-30 12:15 ` [U-Boot] [PATCH 3/5] da830: add support for NAND " nagabhushana.netagunte at ti.com
2011-08-31 8:56 ` Nick Thompson
2011-09-05 8:26 ` Netagunte, Nagabhushana
2011-09-05 9:17 ` Nick Thompson
2011-09-14 5:46 ` Netagunte, Nagabhushana
2011-09-05 9:26 ` Wolfgang Denk
2011-09-14 5:42 ` Netagunte, Nagabhushana
2011-08-30 12:15 ` [U-Boot] [PATCH 4/5] da830: modify the U-Boot prompt string nagabhushana.netagunte at ti.com
2011-08-30 12:16 ` [U-Boot] [PATCH 5/5] da830: modify the MEMTEST start and end address nagabhushana.netagunte at ti.com
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=4E708AEE.4050508@ge.com \
--to=nick.thompson@ge.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