From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] : MACB TX timeout
Date: Fri, 5 Jul 2013 15:49:21 +0800 [thread overview]
Message-ID: <51D67A81.8010701@atmel.com> (raw)
In-Reply-To: <CAD6G_RTBEFm0f-EHk7TsELPoj-v_EZ3iFR01vVuqRCSjXhXBAg@mail.gmail.com>
Hi Jagan,
On 7/5/2013 10:48, Jagan Teki wrote:
> Hi Bo Shen,
>
> Thanks for your info.
>
> On Fri, Jul 5, 2013 at 7:04 AM, Bo Shen <voice.shen@atmel.com> wrote:
>> Hi Jagan Teki,
>>
>>
>> On 7/5/2013 03:36, Jagan Teki wrote:
>>>
>>> Hi,
>>>
>>> Did anyone find this TX timeout issue on macb(gmac)?
>>> I observed this issue when i enable d-cache.
>>>
>>> Log:
>>> ----
>>> zynq-uboot> ping 10.10.70.101
>>> gmac0: PHY present at 7
>>> gmac0: link up, 1000Mbps full-duplex (lpa: 0x3800)
>>> Using gmac0 device
>>> gmac0: TX timeout
>>> gmac0: TX timeout
>>> ping failed; host 10.10.70.101 is not alive
>>
>>
>> Sure, this will happen, as the macb driver is not worked with d-cache
>> enabled.
> Can you point any existing driver that have a d-cache working.
I see the driver of ftgmac100 is doing the thing, but I am not sure
whether the code is merged.
>> If you want to let the macb work with d-cache enable, you should modify the
>> driver.
>>
>> BTW, if you want to enable d-cache, the MMU must be enabled.
> Specific setup to enable to MMU, please point.
> I see that we need to write dram_bank_mmu_setup() and
> arm_init_domains() on d-cache enable code in
> soc folders is that true? please let me know your views.
I am sorry, no information can share with you at this moment.
> --
> Thanks,
> Jagan.
>
Best Regards,
Bo Shen
next prev parent reply other threads:[~2013-07-05 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 19:36 [U-Boot] : MACB TX timeout Jagan Teki
2013-07-05 1:34 ` Bo Shen
2013-07-05 2:48 ` Jagan Teki
2013-07-05 7:49 ` Bo Shen [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-08 6:52 [U-Boot] " Jason Fu
2015-02-08 21:00 ` Andreas Bießmann
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=51D67A81.8010701@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