mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kevin Cernekee <kpc.mtd@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: dedekind@infradead.org, David Brownell <david-b@pacbell.net>,
	Linux MTD <linux-mtd@lists.infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch/rfc 2.6.29 1/2] MTD: driver model updates
Date: Sat, 4 Apr 2009 09:17:46 -0700	[thread overview]
Message-ID: <a95a62fe0904040917w6396443bj3278abbae83df46@mail.gmail.com> (raw)
In-Reply-To: <1238855797.4068.6.camel@macbook.infradead.org>

On 4/4/09, David Woodhouse <dwmw2@infradead.org> wrote:
> I really do think I want this to avoid the need for 64-bit ioctls
> (except maybe MEMERASE64).

So, after adding the sysfs patches, we have two remaining sets of MTD
operations that are limited to 32-bit offsets:

The first set is required to support >4GiB NAND devices: MEMERASE,
MEMREADOOB, and MEMWRITEOOB.

The second set might not make sense at all for most NAND devices:
MEMLOCK, MEMUNLOCK, and MEMGETREGIONINFO.  Maybe it would be nice to
extend them for consistency's sake, but it is possible that they will
never be needed on any >4GiB flash chip.

How would you like to handle these?  Any thoughts on what the
interfaces (sysfs or otherwise) might look like?

Thanks.

  reply	other threads:[~2009-04-04 16:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  7:42 David Brownell
2009-03-31 21:18 ` David Brownell
2009-03-31 23:51   ` Kay Sievers
2009-04-01 13:43     ` Juergen Beisert
2009-04-01  1:17   ` Kevin Cernekee
2009-04-01  3:21     ` David Brownell
2009-04-01  4:49       ` Kevin Cernekee
2009-04-01  6:36         ` David Brownell
2009-04-02 23:41 ` Kevin Cernekee
2009-04-03  7:03   ` Artem Bityutskiy
2009-04-03  7:09     ` Artem Bityutskiy
2009-04-03 20:00     ` Kevin Cernekee
2009-04-04 14:36       ` David Woodhouse
2009-04-04 16:17         ` Kevin Cernekee [this message]
2009-04-04 16:20         ` David Brownell
2009-04-04 16:29           ` David Woodhouse
2009-04-04 17:18       ` David Brownell
2009-04-06  5:34   ` Greg KH
2009-04-03 10:04 ` David Woodhouse
2009-04-03 17:24   ` David Brownell

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=a95a62fe0904040917w6396443bj3278abbae83df46@mail.gmail.com \
    --to=kpc.mtd@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=dedekind@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®