From: David Dillow <dave@thedillows.org>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: "Zhu, Yi" <yi.zhu@intel.com>,
linux-kernel@vger.kernel.org,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Oliver Neukum <oliver@neukum.org>,
Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: [OT] Re: suspend/resume support for driver requires an external firmware
Date: 27 Sep 2004 23:27:54 -0400 [thread overview]
Message-ID: <1096342073.20234.1.camel@ori.thedillows.org> (raw)
In-Reply-To: <200409272214.15992.dtor_core@ameritech.net>
On Mon, 2004-09-27 at 23:14, Dmitry Torokhov wrote:
> On Monday 27 September 2004 09:28 pm, Zhu, Yi wrote:
> > Dmitry Torokhov wrote:
> > > Where do you load your firmware from so that you can bring up
> > > the network so you can mount everything via NFS in the first place?
> >
> > The firmware locates together w/ the driver in the initrd which could be
> > either in the remote PXE server or the local diskettes. It should be
> > also
> > placed somewhere on the NFS root so that it can be picked up to
> > memory during suspend.
> >
>
> Nice try :) but if a card needs a firmware to operate you most likely will
> not be able to access any network resources, including PXE. Only some form
> of local storage can contain kernel and firmware in this case and I would
> think it will be awailable at resume time as well.
The 3Com 3cr990 family also needs external firmware (currently built
into the kernel, but it's on my TODO list to move to the loader), but it
contains enough firmware support in its flash to do PXE.
next prev parent reply other threads:[~2004-09-28 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 2:28 Zhu, Yi
2004-09-28 3:14 ` [OT] " Dmitry Torokhov
2004-09-28 3:27 ` David Dillow [this message]
2004-09-28 15:04 ` Denis Vlasenko
2004-09-28 4:55 ` Patrick Mochel
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=1096342073.20234.1.camel@ori.thedillows.org \
--to=dave@thedillows.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=oliver@neukum.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=yi.zhu@intel.com \
/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
all inboxes | Powered by JetHome®