linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: GPMI-NAND Status?
Date: Tue, 9 Aug 2011 14:40:40 +0800	[thread overview]
Message-ID: <4E40D668.6060907@freescale.com> (raw)
In-Reply-To: <CAHMSPgNf6V8jYLdxFtznNkvLK-R+YN7gUkfbjrxv0WLTDdJmwg@mail.gmail.com>

Hi,
> Hi,
>
> On Tue, Aug 9, 2011 at 7:11 AM, Huang Shijie<b32955@freescale.com>  wrote:
>> Hi Koen:
>>> Anything is good for me.
>>> Could also be useful to make sure we test on the same HW as much as
>>> possible and are using the same source tree.
>>> HW I have:
>>> - mx23evk rev C1
>>> - mx23evk rev B2
>>> - own target hw using mx23 lqfp-128 chip and different type of ddr and
>>> nand.
>>>
>> My test mx23 board is 169BGA package which is different from yours.
>>
>> Could you get the 169BGA package board?
>>
>> I think the DMA timeout is caused by the different package type.
> I suppose my mx23evk is right the same as you have (same revision) and
> this has the bga169 package. My actual target has lqfp128. But on both
> boards I get the same issues.

Could you test my kernel in your side?

I can provide you the sd_loader, kernel.
You can use SD card to store the rootfs.

Best Regards
Huang Shijie
> So I don't think the package type has something to do with the dma
> timeout issue. After all the silicon inside is the same thing.
>
> I'm trying to debug a little further.
>
> Regards,
> Koen
>
>> Best Regards
>> Huang Shijie
>>
>>
>>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>

  reply	other threads:[~2011-08-09  6:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 13:51 GPMI-NAND Status? Wolfram Sang
2011-08-08  6:21 ` Huang Shijie
2011-08-08  9:19   ` Koen Beel
2011-08-08 10:37     ` Huang Shijie
2011-08-08 12:42       ` Koen Beel
2011-08-09  6:36         ` Huang Shijie
2011-08-09  7:58           ` Koen Beel
2011-08-09  8:18             ` Huang Shijie
2011-08-09  8:25               ` Koen Beel
2011-08-09  5:11     ` Huang Shijie
2011-08-09  6:25       ` Koen Beel
2011-08-09  6:40         ` Huang Shijie [this message]
2011-08-09  9:45     ` Wolfram Sang
2011-08-09  9:35   ` Wolfram Sang
2011-08-09 10:54     ` Huang Shijie
2011-08-09 20:42       ` Wolfram Sang
2011-08-08  9:12 ` Huang Shijie
2011-08-09  9:19   ` Wolfram Sang
2011-08-09 10:41     ` Huang Shijie
2011-08-09 11:36       ` Lothar Waßmann
2011-08-14  8:11 ` Ivan Djelic
2011-08-14 18:31   ` Wolfram Sang
2011-08-15  5:41   ` Lothar Waßmann
2011-08-15  6:30     ` Lin Tony-B19295
2011-08-15  8:41       ` Ivan Djelic
2011-08-15  8:29     ` Ivan Djelic
2011-08-15  9:31       ` Lothar Waßmann
2011-08-15 12:54         ` Ivan Djelic
2011-08-15 13:37           ` Lothar Waßmann
2011-08-15 16:34         ` Artem Bityutskiy
2011-08-15 16:18     ` Artem Bityutskiy
2011-08-15 16:22   ` Artem Bityutskiy
2011-08-15 16:57     ` Ivan Djelic

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=4E40D668.6060907@freescale.com \
    --to=b32955@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).