From: Matti Aarnio <matti.aarnio+linux-hotplug@zmailer.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI hotplug question: resources
Date: Wed, 06 Feb 2002 10:20:10 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101299087001430@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101290913112826@msgid-missing>
On Tue, Feb 05, 2002 at 05:17:02PM -0800, Stephen Williams wrote:
> > But I have developed a PCI-card which is "not present" at boot time
> > because there is no firmware in the FPGA which is responsible for PCI
> > communication.
>
> matti.aarnio+linux-hotplug@zmailer.org said:
> > IF your FPGA isn't loaded from e.g. serial flash, but rather from
> > the host processor, then you are screwed...
>
> Actually, what this guy wants to do does have a practical application.
...
Sure, we do that all the time with CARDBUS cards.
They are PCI cards in PCMCIA form.
There still remains an issue of the plugin card needing to
have proper RESET time content in PCI configuration registers
so that PCI autoconfiguration will be possible.
If the FPGA needs to have its "microcode" loaded (ciruitry
definition, actually) from the host, that just can't be
supported. Having a serial-eeprom/flash is simple solution.
The PCI configuration registers on a PCI device are mostly
set to zero at the reset time, but some have hardwired
read content (possibly parts of the registers only,) which
tells the system various things, including device type,
and how much it needs resources. ( plus vendor and other
minor details... )
....
> --
> Steve Williams "The woods are lovely, dark and deep.
/Matti Aarnio
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-02-06 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 11:37 PCI hotplug question: resources Dirk Stieler
2002-02-05 13:55 ` Matti Aarnio
2002-02-06 1:17 ` Stephen Williams
2002-02-06 10:20 ` Matti Aarnio [this message]
2002-02-06 17:55 ` Chris Brand
2002-02-07 8:43 ` Greg KH
2002-02-07 16:42 ` Stephen Williams
2002-02-07 23:51 ` Greg KH
2002-02-08 1:06 ` Donald Becker
2002-02-08 1:34 ` Martin Diehl
2002-02-08 15:44 ` John Carlson
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=marc-linux-hotplug-101299087001430@msgid-missing \
--to=matti.aarnio+linux-hotplug@zmailer.org \
--cc=linux-hotplug@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).