public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: haver@vnet.ibm.com
Cc: John <john@arrows.demon.co.uk>, linux-mtd@lists.infradead.org
Subject: Re: UBI and OneNand
Date: Mon, 06 Nov 2006 15:18:49 +0200	[thread overview]
Message-ID: <1162819129.15435.46.camel@sauron> (raw)
In-Reply-To: <1162806360.5636.19.camel@localhost.localdomain>

Hello,

On Mon, 2006-11-06 at 10:46 +0100, Frank Haverkamp wrote:
> >   1. Should I expect UBI to run on OneNAND without change, or should I
> >      expect to have to write or adapt some code?
> 
> UBI should run on mostly any mtd device. I tried it on NAND as well as
> NOR mtds.
Yeah, in theory you should be able.

> >   4. The UBI faq
> >      http://www.linux-mtd.infradead.org/faq/ubi.html#L_run_ubi says
> >      that when UBI is compiled into the Kernel, you should call
> >      ubi_attach_mtd_dev() to launch the UBI code.  But
> >      ubi_attach_mtd_dev() is now declared static, so I guess the
> >      advice is out of date.  How should UBI be started when compiled
> >      into the kernel?
> 
> We decided that the connection between UBI and its mtd should be made at
> the kernel command line, instead of exporting a function to do this.
I'll update the FAQ.

> >   5. What is the way to get jffs2 running on an UBI partition?  Should
> >      I still be aiming to use gluebi to provide an MTD partition on
> >      top of a UBI partition (whatever that means)? Cook book
> >      instructions would be very helpful.

Just enable "Emulate MTD devices" option in the configuration and UBI
will create an MTD device for each volume, and those MTD devices may be
used to mount JFFS2.

I'll update the FAQ.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2006-11-06 13:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-04  8:22 UBI and OneNand John
2006-11-06  9:46 ` Frank Haverkamp
2006-11-06 13:18   ` Artem Bityutskiy [this message]
2006-11-06 20:16   ` John Smith
2006-11-06 20:54     ` Josh Boyer
  -- strict thread matches above, loose matches on Subject: below --
2006-11-07  2:35 UBI and OneNAND 박경민
2006-11-07  8:50 ` Frank Haverkamp
2006-11-07 10:20   ` John Smith
2006-11-07 11:39     ` Artem Bityutskiy
2006-11-07 11:47       ` Josh Boyer
2006-11-07 14:10         ` Artem Bityutskiy
2006-11-07 14:24           ` Josh Boyer
2006-11-07 14:39             ` Artem Bityutskiy
2006-11-07  9:16 ` Artem Bityutskiy
2006-11-08 16:03 ` Artem Bityutskiy
2006-11-07 12:52 Kyungmin Park
2006-11-08 16:09 ` Artem Bityutskiy

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=1162819129.15435.46.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=haver@vnet.ibm.com \
    --cc=john@arrows.demon.co.uk \
    --cc=linux-mtd@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