From: "Jörn Engel" <joern@logfs.org>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: dhowells <dhowells@redhat.com>, "Carsten Otte" <cotte@de.ibm.com>,
"Jörn Engel" <joern@logfs.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH][MTD] mtdpart.c: allow other drivers to get physical address of partition
Date: Fri, 3 Aug 2007 05:01:55 +0200 [thread overview]
Message-ID: <20070803030144.GA16512@lazybastard.org> (raw)
In-Reply-To: <6934efce0708021856r14a41f89v58f4f156db5e8d5d@mail.gmail.com>
On Thu, 2 August 2007 18:56:46 -0700, Jared Hulbert wrote:
>
> > --- point_phys/include/linux/mtd/mtd.h~point_phys 2007-05-16 02:01:55.000000000 +0200
> > +++ point_phys/include/linux/mtd/mtd.h 2007-08-01 13:49:30.000000000 +0200
> > @@ -136,10 +136,14 @@ struct mtd_info {
> > int (*erase) (struct mtd_info *mtd, struct erase_info *instr);
> >
> > /* This stuff for eXecute-In-Place */
> > - int (*point) (struct mtd_info *mtd, loff_t from, size_t len, size_t *retlen, u_char **mtdbuf);
> > + /* phys is optional and may be set to NULL */
> > + int (*point) (struct mtd_info *mtd, loff_t from, size_t len,
> > + size_t *retlen, void __iomem **virt,
> > + resource_size_t *phys);
>
> Okay so I think __iomem is correct but I'm not sure I understand all
> the ramifications downstream from here.
Interestingly __iomem makes less sense for some RAM-based drivers. So
maybe that part should get removed. The whole patch was just a quick
hack to get an opinion.
> Why resource_size_t?
Because struct map_info has that type for phys.
Jörn
--
Joern's library part 2:
http://www.art.net/~hopkins/Don/unix-haters/tirix/embarrassing-memo.html
next prev parent reply other threads:[~2007-08-03 3:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 0:04 [PATCH][MTD] mtdpart.c: allow other drivers to get physical address of partition Jared Hulbert
2007-07-27 13:48 ` Jörn Engel
2007-07-27 17:05 ` Jared Hulbert
2007-07-27 17:44 ` Jörn Engel
2007-07-27 20:53 ` Jared Hulbert
2007-07-28 11:43 ` Jörn Engel
2007-07-28 21:08 ` Jared Hulbert
2007-07-31 11:55 ` David Woodhouse
2007-07-31 19:55 ` Jared Hulbert
2007-08-01 11:55 ` Jörn Engel
2007-08-03 1:56 ` Jared Hulbert
2007-08-03 3:01 ` Jörn Engel [this message]
2007-08-03 5:23 ` Jared Hulbert
2007-08-03 9:21 ` Jörn Engel
2007-08-03 6:42 ` Jared Hulbert
2007-08-03 12:47 ` Jörn Engel
2007-08-03 22:29 ` Jared Hulbert
2007-08-01 12:18 ` Jörn Engel
2007-08-01 12:59 ` Carsten Otte
2007-08-01 20:37 ` Jared Hulbert
2007-08-01 23:31 ` Jörn Engel
2007-08-02 7:53 ` Carsten Otte
2007-08-02 21:55 ` Jared Hulbert
2007-08-03 7:59 ` Carsten Otte
2007-08-03 9:17 ` Jörn Engel
2007-08-03 11:03 ` Carsten Otte
2007-08-03 11:31 ` Jörn Engel
2007-08-03 12:21 ` Carsten Otte
2007-08-03 12:58 ` Jörn Engel
2007-08-03 13:09 ` David Woodhouse
2007-08-03 13:18 ` Jörn Engel
2007-08-03 19:45 ` Jared Hulbert
2007-08-03 23:02 ` Jörn Engel
2007-08-04 12:33 ` David Woodhouse
2007-08-04 17:47 ` Jared Hulbert
2007-08-06 6:30 ` Carsten Otte
2007-08-03 18:39 ` Jared Hulbert
2007-08-06 6:23 ` Carsten Otte
2007-08-01 18:03 ` Jared Hulbert
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=20070803030144.GA16512@lazybastard.org \
--to=joern@logfs.org \
--cc=cotte@de.ibm.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jaredeh@gmail.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