From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
sf-linux-drivers <linux-net-drivers@solarflare.com>
Subject: Re: [RFC] Online firmware upgrade in non-embedded systems
Date: Wed, 29 Sep 2010 15:34:18 +0300 [thread overview]
Message-ID: <1285763658.2437.112.camel@localhost> (raw)
In-Reply-To: <1285696787.2282.45.camel@achroite.uk.solarflarecom.com>
On Tue, 2010-09-28 at 18:59 +0100, Ben Hutchings wrote:
> Currently the sfc network driver is optionally combined with an MTD
> driver (CONFIG_SFC_MTD) which exposes all upgradable firmware and
> configuration partitions in flash. This works nicely in kernels with
> MTD enabled, but since MTD is mainly used in embedded systems with
> on-board flash it is often disabled in distribution kernels and custom
> kernels alike. This leaves users of sfc unable to upgrade firmware
> without rebuilding the kernel or booting some other distribution. The
> lack of widespread MTD support is a regular cause of support requests.
At least Fedora does have MTD enabled. But I guess commercial
distributions like RHEL might have it disabled (but I did not check),
and I think I could guess the reason for this.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-09-29 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 17:59 [RFC] Online firmware upgrade in non-embedded systems Ben Hutchings
2010-09-28 18:45 ` Alexander Clouter
2010-09-28 22:41 ` Carl-Daniel Hailfinger
2010-09-29 12:35 ` Ben Hutchings
2010-09-29 12:45 ` Carl-Daniel Hailfinger
2010-09-29 13:10 ` Ben Hutchings
2010-09-29 13:43 ` Carl-Daniel Hailfinger
2010-09-29 12:34 ` Artem Bityutskiy [this message]
2010-09-29 12:44 ` Ben Hutchings
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=1285763658.2437.112.camel@localhost \
--to=dedekind1@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).