From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] usb: ci_udc: Allocate the qTD list directly
Date: Tue, 01 Jul 2014 16:51:19 -0600 [thread overview]
Message-ID: <53B33B67.3030606@wwwdotorg.org> (raw)
In-Reply-To: <53B33A9A.50800@posteo.de>
On 07/01/2014 04:47 PM, J?rg Krause wrote:
>
> On 07/02/2014 12:36 AM, Stephen Warren wrote:
>> On 07/01/2014 04:34 PM, J?rg Krause wrote:
>>> On 07/01/2014 01:22 PM, J?rg Krause wrote:
>>>> On 07/01/2014 01:19 PM, Marek Vasut wrote:
>>>>> [snip]
>>>>>>> Can you edit arch/arm/cpu/arm926ejs/cache.c and change the debug() to
>>>>>>> printf() , then re-test please ? I suspect this might trap something
>>>>>>> still. Ah, and please test on u-boot-usb/master with this patch.
>>>>>> No additional output on the console.
>>>>> What does this mean? Do you see warning messages prefixed with
>>>>> "CACHE: " ?
>>>> No messages prefixed with "CACHE: ". Just the usual error message.
>>> I am sorry, but maybe I edited arch/arm/cpu/arm926ejs/ in a another
>>> branch and compiled in u-boot-usb. If I run now tftp with printf enabled
>>> in arch/arm/cpu/arm926ejs/cache.c I get the following "CACHE: " messages:
>>>
>>> CACHE: Misaligned operation at range [40008000, 4000c653]
>>> CACHE: Misaligned operation at range [43fd0b0c, 43fd0b60]
>> That happens right when you first use the UDC driver right? If so, I
>> hope that "[U-Boot] [PATCH 1/6] usb: ci_udc: fix ci_flush_{qh, qtd}
>> calls in ci_udc_probe()" will fix that.
>
> Checkout clean u-boot-usb/master, applied board specific patches and
> applied the mentioned patch. Running tftp three times in a row:
>
...
> U-Boot 2014.07-rc3-g0b32423-dirty (Jul 02 2014 - 00:44:53)
...
> => tftp imx28-airlino.dtb
...
> Loading: ##
> 4.3 MiB/s
> done
> Bytes transferred = 18003 (4653 hex)
> CACHE: Misaligned operation at range [40008000, 4000c653]
OK, that particular error happens well after the network transfer phase
of the tftp command, so is likely nothing to do with ci_udc. It'd be
great if you could track it down and fix it though.
Ah, I bet that 40008000 is your load address; the address that the
downloaded data is being copied to?
next prev parent reply other threads:[~2014-07-01 22:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 23:53 [U-Boot] [PATCH] usb: ci_udc: Allocate the qTD list directly Marek Vasut
2014-06-30 23:55 ` Marek Vasut
2014-07-01 0:04 ` [U-Boot] [PATCH V2] " Marek Vasut
2014-07-01 6:51 ` Jörg Krause
2014-07-01 10:17 ` Marek Vasut
2014-07-01 11:03 ` Jörg Krause
2014-07-01 11:19 ` Marek Vasut
2014-07-01 11:22 ` Jörg Krause
2014-07-01 11:35 ` Marek Vasut
2014-07-01 11:48 ` Jörg Krause
2014-07-01 22:34 ` Jörg Krause
2014-07-01 22:36 ` Stephen Warren
2014-07-01 22:47 ` Jörg Krause
2014-07-01 22:51 ` Stephen Warren [this message]
2014-07-01 22:57 ` Jörg Krause
2014-07-01 23:10 ` Stephen Warren
2014-07-01 15:03 ` Stephen Warren
2014-07-01 15:13 ` Marek Vasut
2014-07-01 15:16 ` Stephen Warren
2014-07-01 15:22 ` Marek Vasut
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=53B33B67.3030606@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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