All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Register PCI host bridge resource earlier
Date: Sun, 08 Apr 2007 16:20:00 +0400	[thread overview]
Message-ID: <4618DDF0.1020604@ru.mvista.com> (raw)
In-Reply-To: <20070408112844.GA7553@alpha.franken.de>

Hello.

Thomas Bogendoerfer wrote:

> PCI based SNI RM machines have their EISA bus behind an Intel PCI/EISA
> bridge. So the PCI IO range must start at 0x0000. Changing that will
> break the PCI bus, because i8259.c already has registered it's IO
> addresses before the PCI bus gets initialized. Below is a patch,
> which will register the PCI host bridge resources inside
> register_pci_controller(). It also changes i8259.c to use insert_region(),
> because request_resource() will fail, if the IO space of the PIT hanging
> of the PCI host bridge (maybe passing the resource parent to
> init_i8259_irqs() is a cleaner fix for that).

    First, I don't understand how PIT and PIC resources may intersect. Then, 
IIUC, using inert_resource() will cause PIT resource be the child of the PIC 
resource which doesn't make sense either.

WBR, Sergei

  reply	other threads:[~2007-04-08 12:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-08 11:28 [PATCH] Register PCI host bridge resource earlier Thomas Bogendoerfer
2007-04-08 12:20 ` Sergei Shtylyov [this message]
2007-04-08 13:12   ` Thomas Bogendoerfer
2007-04-08 13:26     ` Sergei Shtylyov
2007-04-08 13:52       ` Thomas Bogendoerfer
2007-04-08 14:47         ` Sergei Shtylyov
2007-04-08 16:10           ` Thomas Bogendoerfer
2007-04-08 16:58             ` Sergei Shtylyov
2007-04-08 23:24               ` Thomas Bogendoerfer
2007-04-09 15:11                 ` Sergei Shtylyov

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=4618DDF0.1020604@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=tsbogend@alpha.franken.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.