From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Vrabel <dvrabel@cantab.net>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: latest mtd changes broke collie
Date: Thu, 10 Nov 2005 17:41:16 +0000 [thread overview]
Message-ID: <1131644476.24595.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20051110130930.GJ2401@elf.ucw.cz>
On Thu, 2005-11-10 at 14:09 +0100, Pavel Machek wrote:
> > Shouldn't you get hold of the datasheet for the flash chips and fill in
> > this information correctly?
>
> I already have working sharp.c driver... And I do not even know
> manufacturer of the chip, just its ids.
The chip number is LF28F640BX which is a 64MBit device so perhaps Intel
StrataFlash 28F640? That seems to be a fairly common chip...
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Vrabel <dvrabel@cantab.net>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: latest mtd changes broke collie
Date: Thu, 10 Nov 2005 17:41:16 +0000 [thread overview]
Message-ID: <1131644476.24595.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20051110130930.GJ2401@elf.ucw.cz>
On Thu, 2005-11-10 at 14:09 +0100, Pavel Machek wrote:
> > Shouldn't you get hold of the datasheet for the flash chips and fill in
> > this information correctly?
>
> I already have working sharp.c driver... And I do not even know
> manufacturer of the chip, just its ids.
The chip number is LF28F640BX which is a 64MBit device so perhaps Intel
StrataFlash 28F640? That seems to be a fairly common chip...
Richard
next prev parent reply other threads:[~2005-11-10 17:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 22:17 latest mtd changes broke collie Pavel Machek
2005-11-10 0:19 ` Josh Boyer
2005-11-10 9:48 ` Pavel Machek
2005-11-10 2:59 ` Todd Poynor
2005-11-10 9:50 ` Pavel Machek
2005-11-10 10:02 ` David Woodhouse
2005-11-10 10:38 ` Pavel Machek
2005-11-10 10:51 ` David Woodhouse
2005-11-10 10:59 ` Pavel Machek
2005-11-10 11:11 ` David Woodhouse
2005-11-10 11:44 ` Pavel Machek
2005-11-10 12:07 ` Pavel Machek
2005-11-10 13:02 ` David Vrabel
2005-11-10 13:02 ` David Vrabel
2005-11-10 13:09 ` Pavel Machek
2005-11-10 13:09 ` Pavel Machek
2005-11-10 17:41 ` Richard Purdie [this message]
2005-11-10 17:41 ` Richard Purdie
2005-11-10 18:09 ` Richard Purdie
2005-11-10 18:09 ` Richard Purdie
2005-11-10 22:06 ` Pavel Machek
2005-11-10 22:06 ` Pavel Machek
2005-11-10 22:41 ` Pavel Machek
2005-11-10 23:58 ` Todd Poynor
2005-11-10 23:58 ` Todd Poynor
2005-11-11 0:16 ` Pavel Machek
2005-11-11 0:16 ` Pavel Machek
2005-11-11 7:01 ` Ian Campbell
2005-11-12 21:33 ` Pavel Machek
2005-11-12 21:33 ` Pavel Machek
2005-11-13 10:35 ` Ian Campbell
2005-11-13 10:35 ` Ian Campbell
2005-11-14 12:10 ` Pavel Machek
2005-11-14 12:10 ` Pavel Machek
2005-11-13 19:40 ` Todd Poynor
2005-11-13 19:40 ` Todd Poynor
2005-11-14 12:08 ` Pavel Machek
2005-11-14 12:08 ` Pavel Machek
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=1131644476.24595.18.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=dvrabel@cantab.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.