Lets non-standard NAND drivers take advantage of known NAND
chip information.
The initial development of msm nand driver, driver uses the supported
NAND devices information as a hardcoded table. Remove the existing
hardcoded supported flash device table and read the flash device
information from t
On Tue, 2011-03-08 at 05:38 +0530, Murali Nalajala wrote:
> Lets non-standard NAND drivers take advantage of known NAND
> chip information.
>
> The initial development of msm nand driver, driver uses the supported
> NAND devices information as a hardcoded table. Remove the existing
> hardcoded sup
On 3/8/2011 12:50 AM, Artem Bityutskiy wrote:
On Tue, 2011-03-08 at 05:38 +0530, Murali Nalajala wrote:
Lets non-standard NAND drivers take advantage of known NAND
chip information.
The initial development of msm nand driver, driver uses the supported
NAND devices information as a hardcoded tab
On 3/8/2011 11:11 PM, Murali Nalajala wrote:
On 3/8/2011 12:50 AM, Artem Bityutskiy wrote:
On Tue, 2011-03-08 at 05:38 +0530, Murali Nalajala wrote:
Lets non-standard NAND drivers take advantage of known NAND
chip information.
The initial development of msm nand driver, driver uses the support
On Mon, 2011-03-21 at 12:09 +0530, Murali Nalajala wrote:
> On 3/8/2011 11:11 PM, Murali Nalajala wrote:
> > On 3/8/2011 12:50 AM, Artem Bityutskiy wrote:
> >> On Tue, 2011-03-08 at 05:38 +0530, Murali Nalajala wrote:
> >>> Lets non-standard NAND drivers take advantage of known NAND
> >>> chip info
On 3/21/2011 12:42 PM, Artem Bityutskiy wrote:
On Mon, 2011-03-21 at 12:09 +0530, Murali Nalajala wrote:
On 3/8/2011 11:11 PM, Murali Nalajala wrote:
On 3/8/2011 12:50 AM, Artem Bityutskiy wrote:
On Tue, 2011-03-08 at 05:38 +0530, Murali Nalajala wrote:
Lets non-standard NAND drivers take adv
On 3/21/2011 1:28 PM, Murali Nalajala wrote:
On 3/21/2011 12:42 PM, Artem Bityutskiy wrote:
On Mon, 2011-03-21 at 12:09 +0530, Murali Nalajala wrote:
On 3/8/2011 11:11 PM, Murali Nalajala wrote:
On 3/8/2011 12:50 AM, Artem Bityutskiy wrote:
On Tue, 2011-03-08 at 05:38 +0530, Murali Nalajala w
On Tue, 2011-03-22 at 12:11 +0530, Murali Nalajala wrote:
> Still you have any issues/comments?
No, not so far, just have not time now to look closer.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a
On 3/22/2011 1:41 PM, Artem Bityutskiy wrote:
On Tue, 2011-03-22 at 12:11 +0530, Murali Nalajala wrote:
Still you have any issues/comments?
No, not so far, just have not time now to look closer.
Did anybody got a chance to go through the patch?
Thanks,
Murali N
--
Sent by an employee of t
On Wed, 2011-04-06 at 10:08 +0530, Murali Nalajala wrote:
> On 3/22/2011 1:41 PM, Artem Bityutskiy wrote:
> > On Tue, 2011-03-22 at 12:11 +0530, Murali Nalajala wrote:
> >> Still you have any issues/comments?
> >
> > No, not so far, just have not time now to look closer.
> >
> >
> Did anybody got a
Acked-by: Dima Zavin
On Mon, Mar 7, 2011 at 4:08 PM, Murali Nalajala wrote:
> Lets non-standard NAND drivers take advantage of known NAND
> chip information.
>
> The initial development of msm nand driver, driver uses the supported
> NAND devices information as a hardcoded table. Remove the exis
On Mon, Mar 07 2011, Murali Nalajala wrote:
> Lets non-standard NAND drivers take advantage of known NAND
> chip information.
>
> The initial development of msm nand driver, driver uses the supported
> NAND devices information as a hardcoded table. Remove the existing
> hardcoded supported flash d
12 matches
Mail list logo
