From: David Brownell <david-b@pacbell.net>
To: Andrew Victor <andrew@sanpeople.com>
Cc: linux-mtd@lists.infradead.org,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [Bulk] Re: jffs2_flash_writev(): Non-contiguous write to 00825300 with mtd_dataflash
Date: Wed, 29 Nov 2006 23:54:07 -0800 [thread overview]
Message-ID: <200611292354.07946.david-b@pacbell.net> (raw)
In-Reply-To: <1164868198.21731.6.camel@fuzzie.sanpeople.com>
On Wednesday 29 November 2006 10:29 pm, Andrew Victor wrote:
> hi,
>
> > > - device->flags = MTD_CAP_NORFLASH;
> > > + device->flags = MTD_WRITEABLE;
> >
> > That "NORFLASH" flag always seemed bogus to me, but it was at the
> > time the only way to make the MTD core behave.
>
> Wouldn't it be better to introduce a MTD_CAP_DATAFLASH.
> That way if/when more capability flags are added to MTD core, the
> dataflash support will be considered and not forgotten about.
I have no strong opinion one way or another. Structurally it's
maybe a bit more like NAND, and CAP_NANDFLASH == WRITEABLE, so
there might not be a _need_ for such a capability now that some
of that strangeness is gone ...
- Dave
next prev parent reply other threads:[~2006-11-30 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 10:52 jffs2_flash_writev(): Non-contiguous write to 00825300 with mtd_dataflash Haavard Skinnemoen
2006-11-13 7:46 ` Artem Bityutskiy
2006-11-28 11:58 ` Haavard Skinnemoen
2006-11-28 12:36 ` Artem Bityutskiy
2006-11-29 13:26 ` Haavard Skinnemoen
2006-11-29 17:21 ` David Brownell
2006-11-30 6:29 ` Andrew Victor
2006-11-30 7:54 ` David Brownell [this message]
2006-12-01 8:21 ` 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=200611292354.07946.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=andrew@sanpeople.com \
--cc=hskinnemoen@atmel.com \
--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