public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Przemyslaw Marczak <p.marczak@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fat: scripts for prepare and test read fat files
Date: Wed, 17 Dec 2014 09:53:05 +0100	[thread overview]
Message-ID: <54914471.7070702@samsung.com> (raw)
In-Reply-To: <CAPnjgZ1Z39SW_M-dRXA=0pGmSfn-2jCR=9qeGPGjN5mgbALx9w@mail.gmail.com>

Hello Simon,

On 12/16/2014 09:41 PM, Simon Glass wrote:
> Hi Przemyslaw,
>
> On 12 December 2014 at 08:54, Przemyslaw Marczak <p.marczak@samsung.com> wrote:
>>
>> Hello,
>>
>>
>> On 12/12/2014 04:52 PM, Przemyslaw Marczak wrote:
>>>
>>> ---------------------------------------------------------
>>> mktest_files: script for generating random size long name files
>>> ---------------------------------------------------------
>>> Usage:
>>> ./1_mktest_files.sh count
>>>
>>> count - number of files to be generated
>>>
>>> The output directory is: "./test_files"
>>>
>>> ---------------------------------------------------------
>>> copy_files: copy the test_files/* into test partition mount point
>>> ---------------------------------------------------------
>>> Usage:
>>> ./2_copy_files.sh mount_point
>>>
>>> -----------------------------------------------------------
>>> fat_test.sh: test fat read by write commands to the device console
>>> ----------------------------------------------------------
>>> This script send commands to U-Boot console.
>>> First specify few script variables, e.g:
>>> - TTY="/dev/ttyS0"
>>> - MMCDEV=0
>>> - PARTITION=2
>>> - LOAD_ADDR="0x40000000"
>>>
>>> usage:
>>> 1. Target:
>>>      run: ums 0 mmc 0
>>> 2. Run script 1 and 2 to make and copy the test files
>>>      onto the test partition by UMS
>>> 3. This script:
>>>      - set test device $PARTITION and other variables in the script,
>>>        which is required for sending proper commands
>>>      - set $TTY in the script
>>>      run: ./3_fat_test.sh
>>> 4. Compare the crc results on the target and device consoles
>>>      (sorry for the mess on the console)
>>>
>>> Signed-off-by: Przemyslaw Marczak <p.marczak@samsung.com>
>>> ---
>>>    1_mktest_files.sh | 82 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>    2_copy_files.sh   | 20 ++++++++++++++
>>>    3_fat_test.sh     | 38 ++++++++++++++++++++++++++
>>>    3 files changed, 140 insertions(+)
>>>    create mode 100755 1_mktest_files.sh
>>>    create mode 100755 2_copy_files.sh
>>>    create mode 100755 3_fat_test.sh
>>>
>>
>> This is just for some quick test.
>> I will add something more pretty to the sandbox.
>
> Perhaps this should be written in Python? We now have quite a few
> tests and it's getting to the point where we might want to have a way
> to run them all, check results, etc. That would be easier if we could
> import them through some standard interface. For now, perhaps we
> should avoid shell scripts except for really trivial things.
>
> You can bring in the patman libraries (we could break these out into
> another dir but it doesn't seem important):
>
> import os
> import sys
>
> # Bring in the patman libraries
> our_path = os.path.dirname(os.path.realpath(__file__))
> sys.path.append(os.path.join(our_path, 'tools/patman'))
>
> import command
>
> The, for example:
> print command.Output('ls', '-l')
>
> Regards,
> Simon
>

The patch fixes the issue with the "hidden" files, so for looking the 
issue on some other cases I made some simple script. I understand that 
this is not good for a U-Boot tests, and I agree that better is to write 
something automated in the Python for the sandbox.
I think that the fix should be merged.
I can write the test for the sandbox in a free time, but it will take a 
moment, because now I would like to focus on the pmic framework.
The pmic was on hold for too long.

Best regards,
-- 
Przemyslaw Marczak
Samsung R&D Institute Poland
Samsung Electronics
p.marczak at samsung.com

  reply	other threads:[~2014-12-17  8:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 12:01 [U-Boot] [PATCH] fs: fat: read: fix fat16 ls/read issue Przemyslaw Marczak
2014-12-12  0:32 ` Simon Glass
2014-12-12 15:30   ` Przemyslaw Marczak
2014-12-12 15:52     ` [U-Boot] [PATCH] fat: scripts for prepare and test read fat files Przemyslaw Marczak
2014-12-12 15:54       ` Przemyslaw Marczak
2014-12-16 20:41         ` Simon Glass
2014-12-17  8:53           ` Przemyslaw Marczak [this message]
2014-12-16 22:26     ` [U-Boot] [PATCH] fs: fat: read: fix fat16 ls/read issue Simon Glass
2014-12-17  8:53       ` Przemyslaw Marczak
2014-12-17  9:03       ` Przemyslaw Marczak
2014-12-18  3:39         ` Simon Glass
2014-12-18 10:26           ` Przemyslaw Marczak
2014-12-18 13:14             ` Simon Glass
2014-12-18 13:31               ` Przemyslaw Marczak
2014-12-18 13:36                 ` Simon Glass
2014-12-18 13:41                   ` Przemyslaw Marczak
2014-12-18 13:47 ` Simon Glass
2014-12-18 14:06   ` Przemyslaw Marczak
2014-12-18 14:32   ` Przemyslaw Marczak
2014-12-18 14:34     ` Simon Glass
2014-12-18 14:40       ` Przemyslaw Marczak
2014-12-18 14:56         ` Simon Glass
2014-12-18 15:12           ` Przemyslaw Marczak
2014-12-18 15:21 ` [U-Boot] [PATCH v2] " Przemyslaw Marczak
2014-12-18 16:14   ` [U-Boot] [PATCH v3] " Przemyslaw Marczak
2015-01-07 15:12     ` [U-Boot] [U-Boot,v3] " Tom Rini

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=54914471.7070702@samsung.com \
    --to=p.marczak@samsung.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