From: Huang Shijie <b32955@freescale.com>
To: "Paul B. Henson" <henson@acm.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: i.MX28 gpmi-nand underlying geometry
Date: Tue, 26 Mar 2013 10:17:37 +0800 [thread overview]
Message-ID: <51510541.8020209@freescale.com> (raw)
In-Reply-To: <515099D4.1090605@acm.org>
于 2013年03月26日 02:39, Paul B. Henson 写道:
> Thanks much for the quick response and the offer of assistance. Would
> it be possible to have the information programmatically available such
> that kobs-ng (or some other application) could read/determine it
> itself either via a sysfs node like the previous driver or some other
> method to export the information to user space? A manually triggered
> debug log would remove the need to boot an older kernel to determine
> the information, but would still require a user to transcribe the
> information from the log to kobs-ng. If the sysfs node or other export
> mechanism was only available if a particular command line option was
> supplied to the kernel to avoid contaminating the environments of
> people not interested in such a feature that would be fine.
The latest kobs-ng uses the same method as the kernel to calculate the
necessary parameters.
It does not depend on the sysfs node any more. So do not worry about this.
You can download the latest kobs-ng for imx6q from freescale's
website(sorry, I do not know the weblink.)
thanks
Huang Shijie
next prev parent reply other threads:[~2013-03-26 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 3:18 i.MX28 gpmi-nand underlying geometry Paul B. Henson
2013-03-25 7:19 ` Huang Shijie
2013-03-25 18:39 ` Paul B. Henson
2013-03-26 2:17 ` Huang Shijie [this message]
2013-03-26 20:49 ` Paul B. Henson
2013-05-10 11:43 ` 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=51510541.8020209@freescale.com \
--to=b32955@freescale.com \
--cc=henson@acm.org \
--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;
as well as URLs for NNTP newsgroup(s).