linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio+linux-hotplug@zmailer.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI hotplug question: resources
Date: Tue, 05 Feb 2002 13:55:01 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101291737303871@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101290913112826@msgid-missing>

On Tue, Feb 05, 2002 at 12:37:20PM +0100, Dirk Stieler wrote:
> Hello hotplug developers,
> 
> I am a "hotplug newbie" and maybe this is not the right place for my
> question, so please excuse if this thread is wrong here.
> 
> I have a standard personal computer, not really a hotplug system.
> 
> 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.

   You really should create circuitry definitions which implement
   the reset-time initial state for PCI "hotplugging".

   - Type data
   - IO address space size
   - MEM address space size
   - Number of IRQs

   (and whatnot else there was..)

   Then any BIOS will do the startup job for you.
   (And even Linux can do it by reworking the PCI configuration datasets.)

> After the configuration of the FPGA I have to determine which
> PCI-resources I can use for the card ( IO, mem, IRQ ) and assign this
> resources to it.
> 
> You know what I mean?
> How can I solve this problem?
> Maybe it's trivial for you but I haven't found an solution yet.

   All of that is just basic PCI specification stuff.

   IF your FPGA isn't loaded from e.g. serial flash, but rather from
   the host processor, then you are screwed...

> Thank you, regards,
>    Dirk Stieler

/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

  reply	other threads:[~2002-02-05 13:55 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 [this message]
2002-02-06  1:17 ` Stephen Williams
2002-02-06 10:20 ` Matti Aarnio
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-101291737303871@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).