All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "武井 克明" <takei744@oki.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Questions about ubifs,ubi and mtd?
Date: Mon, 10 Dec 2018 15:46:34 +0100	[thread overview]
Message-ID: <87o99txwvp.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <TY2PR01MB2700AD659601C0341B5C06929DA50@TY2PR01MB2700.jpnprd01.prod.outlook.com>


On Mon, Dec 10 2018, 武井 克明 wrote:

> Hi all,
>
> We are developing the product using file system using ubi, ubifs on hardware with NAND flash memory.
>
> Although the development of the product was completed, we are seeking your help as the customer who is using it is having trouble with it.
>
> The product we have developed has 6 MTD partitions for NAND flash memory.
> These consist of 6 MTDs named 'kernel-a' 'kernel-b', 'rootfs-a', 'rootfs-b', 'data-1', 'data-2', and online program only accesses 'data-1' and 'data-2' for write access.
> Nevertheless, when loading our program from 'rootfs-a', trying to read the inode with the ubifs_read_node() function will result in "bad node type" (ex: 193 but expected 9) and the LEB can not be read with the expected value. (Even though you do not have write access to rootfs)
>
> Is there anyone who encountered such a problem? Is there patch?
>
> Please let me know, if you have any questions.
>
> Best regards,
> Katsuaki Takei/Oki Electric Industry Co., Ltd./JP

Hi. I think you're on the wrong mailing list (git@). You probably want
to contact one of the linux lists, perhaps
http://lists.infradead.org/mailman/listinfo/linux-mtd ?

  reply	other threads:[~2018-12-10 14:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 12:22 Questions about ubifs,ubi and mtd? 武井 克明
2018-12-10 14:46 ` Ævar Arnfjörð Bjarmason [this message]
2018-12-11  0:42   ` 武井 克明
  -- strict thread matches above, loose matches on Subject: below --
2018-12-11 14:08 武井 克明
2018-12-11 17:10 ` Richard Weinberger
2018-12-12  1:07   ` 武井 克明
2018-12-12  9:20     ` Richard Weinberger
2018-12-13 10:45       ` 武井 克明
2018-12-13 11:32         ` Martin Lund
2018-12-13 11:38           ` Richard Weinberger
2018-12-13 12:04             ` 武井 克明
2018-12-13 11:35         ` Richard Weinberger
2018-12-13 17:18           ` Steve deRosier
2018-12-13 21:16             ` Richard Weinberger
2018-12-13 22:22               ` Steve deRosier
2018-12-15 11:24                 ` Miquel Raynal
2018-12-14  6:18               ` Katsuaki Takei/OKI/JP
2018-12-14  6:11             ` Katsuaki Takei/OKI/JP

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=87o99txwvp.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=takei744@oki.com \
    /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.