From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 29E05B7171 for ; Wed, 17 Jun 2009 01:34:42 +1000 (EST) MIME-Version: 1.0 In-Reply-To: References: <1244203514-12516-3-git-send-email-w.sang@pengutronix.de> <1245087807.3185.0@antares> <20090616091801.GC21321@pengutronix.de> <20090616132005.GD21321@pengutronix.de> Date: Tue, 16 Jun 2009 09:34:38 -0600 Message-ID: Subject: Re: [PATCH V2 2/2] mtd/maps/mtd-ram: add an of-platform driver From: Grant Likely To: Wolfram Sang Content-Type: multipart/alternative; boundary=001e68378987aaf931046c78e926 Cc: devicetree-discuss@ozlabs.org, =?ISO-8859-1?Q?Albrecht_Dre=DF?= , linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org, Ben Dooks , David Woodhouse List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --001e68378987aaf931046c78e926 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Okay, fair enough. I wasn't paying very close attention when I replied. It still seems awkward to me, but not enough to object (ie. It's not dangerous). g. On Jun 16, 2009 7:20 AM, "Wolfram Sang" wrote: > > Grant wondered if we need a bankwidth. IMHO it is needed for now, but I don't > > know if this i... Maybe there is a misunderstanding here. I am not talking about Albrecht's case. What I replied to your concern is that bankwidth is used(!) in the underlying map-ram-driver in mapram_erase() at the moment. Whether this is really needed could be discussed perhaps, but is beyond the scope of this patch series IMHO. I'd think this can be addressed in a later series, if needed, although this could mean that the binding will change (bank-width becoming optional). Regards, Wolfram -- Pengutronix e.K. | Wolfram Sang ... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAko3nAUACgkQD27XaX1/VRtTkACfW0aUMJHrU3m4DCel0pm5fA6J WaQAnjGo5fn6JvMHt3Ke/xFTGB1uYT6p =V9t5 -----END PGP SIGNATURE----- --001e68378987aaf931046c78e926 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Okay, fair enough.=A0 I wasn't paying very close attention when I re= plied.=A0 It still seems awkward to me, but not enough to object (ie. It= 9;s not dangerous).

g.

On Jun 16, 2009 7:20 AM, "Wolfram Sang&qu= ot; <w.sang@pengutronix.de&= gt; wrote:

> > Grant wondered if we= need a bankwidth. IMHO it is needed for now, but I don't > > know if this i...

Maybe there is a misunderstanding her= e. I am not talking about Albrecht's case.
What I replied to your concern is that bankwidth is used(!) in the underlyi= ng
map-ram-driver in mapram_erase() at the moment. Whether this is really need= ed
could be discussed perhaps, but is beyond the scope of this patch series IM= HO.
I'd think this can be addressed in a later series, if needed, although = this
could mean that the binding will change (bank-width becoming optional).

Regards, Wolfram --=20 Pengutronix e.K. | Wolfram Sang ..= .


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAko3nAUACgkQD27XaX1/VRtTkACfW0aUMJHrU3m4DCel0pm5fA6J
WaQAnjGo5fn6JvMHt3Ke/xFTGB1uYT6p
=3DV9t5
-----END PGP SIGNATURE-----

--001e68378987aaf931046c78e926--