linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hiroshi Aono <h-aono@ap.jp.nec.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hot Plug I/O Node spec 0.2.1
Date: Tue, 05 Feb 2002 12:00:02 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101291044916459@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101218212231808@msgid-missing>

At Mon, 4 Feb 2002 21:39:04 -0800,
Greg KH wrote:
> 
> On Tue, Feb 05, 2002 at 02:16:20PM +0900, Hiroshi Aono wrote:
> > At Sun, 3 Feb 2002 00:19:15 -0800, Greg KH wrote:
> > > 
> > > What is the "Object Redistration Interface" going to look like?  What is
> > > needed to be sent from a configuration file to the IO Node resource
> > > manager?  Doesn't the IO Node resource manager get all of the
> > > information it needs from the BIOS/ACPI interface?
> > 
> > I expect that this mainly works for debugging.
> > I think the hardware like this may not work sufficiently at first.
> > or it may be used for non-ACPI machine.
> > This configuration file will be stored hardware information.
> 
> Like what?  A snapshot of the device tree that was present the last time
> we powered down?

Yes, I think that even what you think is OK.

> 
> > Of course IO Node resource manager should get all information from
> > BIOS/ACPI.
> > I think the IO node driver and the Object Registration
> > interface between IO node resource manager should have same interface.
> 
> And what do you see that interface being?  

I don't have a concrete idea. but I think it's good to use
 hotplug filessystem or something.

> 
> > > "pic"?  What is this?
> > 
> > "pic" means programmable interrupt controller like an IOSAPIC.
> 
> Ok, but why does it need to have an entry in the filesystem?  Can you
> turn it on and off, with the same kinds of attributes the slots have?

Certainly.
We don't need to show pic to a user.

> > > How?  Doesn't a IO node just show up as a PCI device being added to the
> > > system?
> > 
> > Our IO node doesn't show up as a PCI device.
> > Does IBM work so?
> 
> No, the IO node never shows up at all, from what I can tell.  But all of
> the pci devices show up all at once :)

I imagine that each PCI devices should be managed by PCI hotplug
driver, and it might not be loaded first. Also it's no problem that
PCI hotplug driver is built in or is loaded in advance.

In brief, I expect that it works like a current pci_dev hotplug framework.

Regards,
---
Hiroshi Aono, NEC Solutions
(h-aono@ap.jp.nec.com)

_______________________________________________
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

      parent reply	other threads:[~2002-02-05 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28  1:36 Hot Plug I/O Node spec 0.2.1 Hiroshi Aono
2002-02-03  1:59 ` David Brownell
2002-02-05  5:39 ` Greg KH
2002-02-05 12:00 ` Hiroshi Aono [this message]

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-101291044916459@msgid-missing \
    --to=h-aono@ap.jp.nec.com \
    --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).