All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Gleb O. Raiko" <raiko@niisi.msk.ru>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: arch/mips/pci* stuff
Date: Fri, 24 Aug 2001 15:33:35 +0200	[thread overview]
Message-ID: <20010824153335.A948@dea.linux-mips.net> (raw)
In-Reply-To: <3B862487.EF22D143@niisi.msk.ru>; from raiko@niisi.msk.ru on Fri, Aug 24, 2001 at 01:55:19PM +0400

On Fri, Aug 24, 2001 at 01:55:19PM +0400, Gleb O. Raiko wrote:

> Could somebody, please, explain me what arch/mips/pci* stuff is for? My
> understanding is drivers/pci code shall setup everything except proper
> placing in PCI MEM/IO spaces and irqs. The code in arch/mips/pci*
> contains much more.
> 
> Anyway, drivers/pci code provides enough fixup interface, doesn't it ?
> 
> BTW, if the code in arch/mips/pci* is really required how about
> fine-grained placing, like in sparc64?

Drivers/pci/ does no full initialization of PCI busses which is necessary
on some systems where the firmware doesn't.  The code in the kernel tree
isn't yet complete; I still have two patches left to merge.

  Ralf

  reply	other threads:[~2001-08-24 17:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-24  9:55 arch/mips/pci* stuff Gleb O. Raiko
2001-08-24 13:33 ` Ralf Baechle [this message]
2001-08-24 16:13 ` Pete Popov
2001-08-24 17:57 ` Jun Sun
2001-08-24 18:20   ` Ralf Baechle
2001-08-28 11:22   ` Gleb O. Raiko
2001-09-11 19:19     ` Jun Sun
2001-09-17 11:21       ` Gleb O. Raiko
2001-09-17 22:37         ` Jun Sun
2001-09-19  8:23           ` Gleb O. Raiko
2001-09-19 18:00             ` Jun Sun

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=20010824153335.A948@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=raiko@niisi.msk.ru \
    /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.