From: "Jörn Engel" <joern@logfs.org>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: linux-mtd-bounces@lists.infradead.org,
'Bruce Leonard' <brucle@earthlink.net>,
Bruce_Leonard@selinc.com, linux-kernel@vger.kernel.org,
Tim Anderson <tanderson@mvista.com>,
linux-mtd@lists.infradead.org,
'Andrew Morton' <akpm@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 2/2][MTD] Add support for > 2GiB MTD devices
Date: Fri, 29 Aug 2008 12:23:26 +0200 [thread overview]
Message-ID: <20080829102326.GA27647@logfs.org> (raw)
In-Reply-To: <1219988887.4036.7.camel@sauron>
On Fri, 29 August 2008 08:48:07 +0300, Artem Bityutskiy wrote:
> On Wed, 2008-08-27 at 17:25 +0200, Jörn Engel wrote:
> >
> > Could be useful, I don't mind you sending a patch. However, does this
> > means that MEMGETINFO64 or some other ioctl should not be done? Should
> > flash_erase open, read and close 8 seperate files instead of doing a
> > single ioctl? And should our support for large devices wait for the
> > sysfs support that has been talked about and not done for about two
> > years already?
>
> Up to dwmw2, but I do not mind if the answer to all the above questions
> is "yes" :-)
Well, I personally think a "yes" to the last question would be utter
madness. Whoever answers that should better come up with an alternative
patch for sysfs support pronto.
Large flashes are not a one-off cases where a single manufacturer had a
rather bizarre design. Their numbers will continually increase. And
not supporting an ever-increasing class of hardware is simply not an
option.
Jörn
--
on a false concept. This concept is that
people actually want to look at source code.
-- Rob Enderle
next prev parent reply other threads:[~2008-08-29 10:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25387440.1219370455174.JavaMail.root@elwamui-cypress.atl.sa.earthlink.net>
2008-08-26 23:55 ` [PATCH 2/2][MTD] Add support for > 2GiB MTD devices Andrew Morton
2008-08-27 1:21 ` Bruce_Leonard
2008-08-27 1:40 ` Tim Anderson
2008-08-27 2:08 ` Andrew Morton
2008-08-27 2:42 ` Bruce_Leonard
2008-08-27 5:56 ` Artem Bityutskiy
2008-08-27 6:01 ` Tim Anderson
2008-08-27 6:03 ` Artem Bityutskiy
2008-08-27 6:20 ` Tim Anderson
2008-08-27 6:35 ` David Woodhouse
2008-08-27 6:49 ` Ricard Wanderlof
2008-08-27 7:08 ` Artem Bityutskiy
2008-08-27 7:10 ` Bruce Leonard
2008-08-27 6:38 ` Artem Bityutskiy
2008-08-27 8:39 ` Alan Cox
2008-08-27 9:01 ` David Woodhouse
2008-08-27 14:34 ` Jörn Engel
2008-08-27 14:47 ` Artem Bityutskiy
2008-08-27 15:25 ` Jörn Engel
2008-08-29 5:48 ` Artem Bityutskiy
2008-08-29 10:23 ` Jörn Engel [this message]
2008-08-29 12:19 ` David Woodhouse
2008-08-27 19:44 ` Trent Piepho
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=20080829102326.GA27647@logfs.org \
--to=joern@logfs.org \
--cc=Bruce_Leonard@selinc.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=brucle@earthlink.net \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd-bounces@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tanderson@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox