From: Paul Fertser <fercerpav@gmail.com>
To: John Crispin <blogic@openwrt.org>
Cc: openwrt-devel@lists.openwrt.org, linux-mtd@lists.infradead.org
Subject: Re: Rebooting boards with > 16M SPI flash
Date: Thu, 09 Jul 2015 09:53:55 +0300 [thread overview]
Message-ID: <87fv4xzurg.fsf@home.paul.comp> (raw)
In-Reply-To: <559E0C3D.6090008@openwrt.org> (John Crispin's message of "Thu, 09 Jul 2015 07:53:01 +0200")
Hi John,
John Crispin <blogic@openwrt.org> writes:
> looks good to me but i will run this past linux-mtd and ask them for an
> opinion before merging it.
This patch was meant as a quick "hack" rather than a complete solution,
that's why I didn't bother adding proper commit message, S-o-b etc. But
since I'm the author, I can do that promptly, whenever that's needed.
The main limitation is that I checked only a single datasheet (likely
Winbond) so other models might require different treatment. Another is
that such a patch is mostly a bad substitute for proper hardware design.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
parent reply other threads:[~2015-07-09 6:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <559E0C3D.6090008@openwrt.org>]
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=87fv4xzurg.fsf@home.paul.comp \
--to=fercerpav@gmail.com \
--cc=blogic@openwrt.org \
--cc=linux-mtd@lists.infradead.org \
--cc=openwrt-devel@lists.openwrt.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