From: David Woodhouse <dwmw2@infradead.org>
To: David Brownell <david-b@pacbell.net>
Cc: 'Bernd Schmidt' <bernd.schmidt@analog.com>,
Sudhakar Rajashekhara <sudhakar.raj@ti.com>,
'Nicolas Pitre' <nico@fluxnic.net>,
'Kevin Hilman' <khilman@deeprootsystems.com>,
linux-kernel@vger.kernel.org,
'David Howells' <dhowells@redhat.com>,
'David Brownell' <dbrownell@users.sourceforge.net>,
linux-mtd@lists.infradead.org,
'Andrew Morton' <akpm@linux-foundation.org>
Subject: RE: [PATCH 1/2] mtdpart: memory accessor interface for MTD layer
Date: Wed, 04 Aug 2010 11:12:05 +0100 [thread overview]
Message-ID: <1280916725.19499.12.camel@localhost> (raw)
In-Reply-To: <54038.80733.qm@web180305.mail.gq1.yahoo.com>
On Wed, 2010-07-07 at 04:08 -0700, David Brownell wrote:
>
> I think the short answer is that the callout is
> what provides the board drivers enough information
> to make the correct calls.
I don't see how.
The only information it passes to the callout is the information it was
already *given* in the partition structure.
I'm more inclined to believe Sudhakar's claim that you'll get an
'initialization sequence problem', although I'm not sure I believe it
can't be solved in a better way than this.
I'm also unhappy that it only works on partitioned devices -- that seems
wrong.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
WARNING: multiple messages have this Message-ID (diff)
From: David Woodhouse <dwmw2@infradead.org>
To: David Brownell <david-b@pacbell.net>
Cc: "'Kevin Hilman'" <khilman@deeprootsystems.com>,
Sudhakar Rajashekhara <sudhakar.raj@ti.com>,
"'Bernd Schmidt'" <bernd.schmidt@analog.com>,
"'Nicolas Pitre'" <nico@fluxnic.net>,
linux-kernel@vger.kernel.org,
"'David Howells'" <dhowells@redhat.com>,
"'David Brownell'" <dbrownell@users.sourceforge.net>,
linux-mtd@lists.infradead.org,
"'Andrew Morton'" <akpm@linux-foundation.org>
Subject: RE: [PATCH 1/2] mtdpart: memory accessor interface for MTD layer
Date: Wed, 04 Aug 2010 11:12:05 +0100 [thread overview]
Message-ID: <1280916725.19499.12.camel@localhost> (raw)
In-Reply-To: <54038.80733.qm@web180305.mail.gq1.yahoo.com>
On Wed, 2010-07-07 at 04:08 -0700, David Brownell wrote:
>
> I think the short answer is that the callout is
> what provides the board drivers enough information
> to make the correct calls.
I don't see how.
The only information it passes to the callout is the information it was
already *given* in the partition structure.
I'm more inclined to believe Sudhakar's claim that you'll get an
'initialization sequence problem', although I'm not sure I believe it
can't be solved in a better way than this.
I'm also unhappy that it only works on partitioned devices -- that seems
wrong.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-08-04 10:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 20:41 [PATCH 1/2] mtdpart: memory accessor interface for MTD layer Kevin Hilman
2010-03-16 20:41 ` Kevin Hilman
2010-04-08 8:10 ` Artem Bityutskiy
2010-04-08 8:10 ` Artem Bityutskiy
2010-05-13 23:50 ` David Woodhouse
2010-05-13 23:50 ` David Woodhouse
2010-07-07 10:56 ` Sudhakar Rajashekhara
2010-07-07 11:08 ` David Brownell
2010-07-07 11:08 ` David Brownell
2010-07-08 15:10 ` Sudhakar Rajashekhara
2010-07-08 16:00 ` David Brownell
2010-08-04 10:12 ` David Woodhouse [this message]
2010-08-04 10:12 ` David Woodhouse
2010-08-04 10:31 ` David Brownell
2010-08-04 10:31 ` David Brownell
2010-08-04 11:08 ` David Woodhouse
2010-08-04 11:08 ` David Woodhouse
2010-08-04 11:27 ` David Brownell
2010-08-04 11:27 ` David Brownell
2010-08-06 6:48 ` Sudhakar Rajashekhara
2010-08-08 12:23 ` David Woodhouse
2010-08-08 12:23 ` David Woodhouse
2010-08-09 11:55 ` Sudhakar Rajashekhara
-- strict thread matches above, loose matches on Subject: below --
2010-10-01 21:16 [patch " akpm
2010-10-02 14:09 ` Artem Bityutskiy
2010-10-02 14:44 ` David Woodhouse
2010-10-04 14:28 ` Sudhakar Rajashekhara
2010-10-02 19:09 ` Andrew Morton
2010-10-20 22:59 akpm
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=1280916725.19499.12.camel@localhost \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bernd.schmidt@analog.com \
--cc=david-b@pacbell.net \
--cc=dbrownell@users.sourceforge.net \
--cc=dhowells@redhat.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@fluxnic.net \
--cc=sudhakar.raj@ti.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.