All of lore.kernel.org
 help / color / mirror / Atom feed
From: gianluca <gianlucarenzi@eurekelettronica.it>
To: Huang Shijie <b32955@freescale.com>
Cc: dedekind1@gmail.com, koen.beel.barco@gmail.com,
	w.sang@pengutronix.de, marek.vasut@gmail.com,
	linux-mtd@lists.infradead.org, shijie8@gmail.com,
	s.hauer@pengutronix.de, linux-arm-kernel@lists.infradead.org,
	"Lothar Waßmann" <LW@KARO-electronics.de>
Subject: Re: [PATCH v12 0/3] add the GPMI controller driver for IMX23/IMX28
Date: Thu, 15 Sep 2011 17:24:16 +0200	[thread overview]
Message-ID: <4E7218A0.2020309@eurekelettronica.it> (raw)
In-Reply-To: <4E71CDB2.4000205@freescale.com>

Sorry for intrusion in this discussion, but:

Huang Shijie wrote:
>> channels are being used concurrently. The GPMI driver will bail out
>> with the timeout error while the MMC driver obviously has no timeout
>> check for this situation.
>>
>> I can mostly rule out HW problems, because the same board works
>> perfectly well with WindowsCE (tested with a copy operation between
>> flash and SD card).
>>
>>
>> Lothar Waßmann

@Lothar: Probably WinCE with a copy operation between flash and SD is 
not reliable as synchronous as opposed dd command in the previous mail.

dd is sync when: dd if=/dev/mtd... of=/dev/mmc...

dd is async when:

# dd if=/dev/mtd of=/mnt/somewhere/file1 &
# dd if=/mnt/somewhere/file2 of=/dev/mmc &

Or even the worst scenario:

# dd if=/dev/mtdX of=/dev/null &
# dd if=/dev/urandom of=/dev/mmcX &
# dd if=/dev/mmcX of=/dev/null &
# dd if=/dev/urandom of=/dev/mtdX &

Just my .2 cents.

Best regards,
-- 
            ,,,
           (o o)
======oOO==(_)==OOo======

Gianluca Renzi
R&D
phone: +39.0542.609120
fax:   +39.0542.609212

       .oooO  Oooo.
======(   )==(   )=======
        \ (    ) /
         \_)  (_/

WARNING: multiple messages have this Message-ID (diff)
From: gianlucarenzi@eurekelettronica.it (gianluca)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v12 0/3] add the GPMI controller driver for IMX23/IMX28
Date: Thu, 15 Sep 2011 17:24:16 +0200	[thread overview]
Message-ID: <4E7218A0.2020309@eurekelettronica.it> (raw)
In-Reply-To: <4E71CDB2.4000205@freescale.com>

Sorry for intrusion in this discussion, but:

Huang Shijie wrote:
>> channels are being used concurrently. The GPMI driver will bail out
>> with the timeout error while the MMC driver obviously has no timeout
>> check for this situation.
>>
>> I can mostly rule out HW problems, because the same board works
>> perfectly well with WindowsCE (tested with a copy operation between
>> flash and SD card).
>>
>>
>> Lothar Wa?mann

@Lothar: Probably WinCE with a copy operation between flash and SD is 
not reliable as synchronous as opposed dd command in the previous mail.

dd is sync when: dd if=/dev/mtd... of=/dev/mmc...

dd is async when:

# dd if=/dev/mtd of=/mnt/somewhere/file1 &
# dd if=/mnt/somewhere/file2 of=/dev/mmc &

Or even the worst scenario:

# dd if=/dev/mtdX of=/dev/null &
# dd if=/dev/urandom of=/dev/mmcX &
# dd if=/dev/mmcX of=/dev/null &
# dd if=/dev/urandom of=/dev/mtdX &

Just my .2 cents.

Best regards,
-- 
            ,,,
           (o o)
======oOO==(_)==OOo======

Gianluca Renzi
R&D
phone: +39.0542.609120
fax:   +39.0542.609212

       .oooO  Oooo.
======(   )==(   )=======
        \ (    ) /
         \_)  (_/

  reply	other threads:[~2011-09-15 15:24 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08  2:47 [PATCH v12 0/3] add the GPMI controller driver for IMX23/IMX28 Huang Shijie
2011-09-08  2:47 ` Huang Shijie
2011-09-08  2:47 ` [PATCH v12 1/3] MTD : add the common code for GPMI-NAND controller driver Huang Shijie
2011-09-08  2:47   ` Huang Shijie
2011-09-08  2:47 ` [PATCH v12 2/3] MTD : add helper functions library and header files for GPMI NAND driver Huang Shijie
2011-09-08  2:47   ` Huang Shijie
2011-09-08  2:47 ` [PATCH v12 3/3] MTD : add GPMI-NAND driver in the config and Makefile Huang Shijie
2011-09-08  2:47   ` Huang Shijie
2011-09-09 19:56 ` [PATCH v12 0/3] add the GPMI controller driver for IMX23/IMX28 Koen Beel
2011-09-09 19:56   ` Koen Beel
2011-09-11 10:31 ` Artem Bityutskiy
2011-09-11 10:31   ` Artem Bityutskiy
2011-09-12  4:34   ` Huang Shijie
2011-09-12  4:34     ` Huang Shijie
2011-09-15  7:55 ` Lothar Waßmann
2011-09-15  7:55   ` Lothar Waßmann
2011-09-15  8:26   ` Huang Shijie
2011-09-15  8:28   ` Huang Shijie
2011-09-15  8:28     ` Huang Shijie
2011-09-15  9:12     ` Lothar Waßmann
2011-09-15  9:12       ` Lothar Waßmann
2011-09-15  9:20       ` Huang Shijie
2011-09-15  9:20         ` Huang Shijie
2011-09-26  7:42       ` Huang Shijie
2011-09-26  7:42         ` Huang Shijie
2011-09-15 10:04   ` Huang Shijie
2011-09-15 10:04     ` Huang Shijie
2011-09-15 15:24     ` gianluca [this message]
2011-09-15 15:24       ` gianluca
2011-09-16  7:50       ` Lothar Waßmann
2011-09-16  7:50         ` Lothar Waßmann
2011-09-16 13:43     ` Lothar Waßmann
2011-09-16 13:43       ` Lothar Waßmann
2011-09-18 11:40       ` Huang Shijie
2011-09-18 11:40         ` Huang Shijie

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=4E7218A0.2020309@eurekelettronica.it \
    --to=gianlucarenzi@eurekelettronica.it \
    --cc=LW@KARO-electronics.de \
    --cc=b32955@freescale.com \
    --cc=dedekind1@gmail.com \
    --cc=koen.beel.barco@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shijie8@gmail.com \
    --cc=w.sang@pengutronix.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.