From: Pete Popov <ppopov@pacbell.net>
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 09:13:21 -0700 [thread overview]
Message-ID: <3B867D21.50007@pacbell.net> (raw)
In-Reply-To: 3B862487.EF22D143@niisi.msk.ru
Gleb O. Raiko wrote:
> Hello,
>
> 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?
I assume you're talking about the new arch/mips/kernel/pci* code? Yes, there's
is duplication in arch/mips/kernel/pci.c and what's in drivers/pci. However,
there wasn't a single complete function for mips that would get the job done.
The result was that every single board with pci support did its own thing and it
was getting ugly very quickly. Just search through all the embedded boards
directories and you'll see what I'm talking about. The other important new file
is arch/mips/kernel/pci_auto.c. If you enable pci auto in config.in, the pci
resources will be assigned by pci_auto.c. Thus, you don't need to rely on boot
code to do that anymore, which I think is a good thing.
Pete
next prev parent reply other threads:[~2001-08-24 16:13 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
2001-08-24 16:13 ` Pete Popov [this message]
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=3B867D21.50007@pacbell.net \
--to=ppopov@pacbell.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox