From: Steve Rossi <srossi@ccrl.mot.com>
To: Dan Malek <dan@netx4.com>
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Question on QSPAN Driver
Date: Mon, 20 Mar 2000 13:44:35 -0600 [thread overview]
Message-ID: <38D67FA3.D00A5110@ccrl.mot.com> (raw)
In-Reply-To: 38D66069.AA538C28@embeddededge.com
Dan Malek wrote:
>
> > So here are my questions:
> > 1. Why doesn't qspan_init ever get called before the PCI bus is scanned?
>
> That is the job of something during the boot process before the Linux
> kernel is started.
>
> > 2. Should the pci_scanner function in arch/ppc/mbxboot/pci.c be called
> > in
> > place of the normal pci_scan_bus() function in drivers/pci/pci.c?
>
> No, those functions are very different. The functions in 'mbxboot'
> are used to initialize and map the PCI bus. The functions in the
> Linux kernel are discovery functions.
Ok, now this is making a whole lot more sense to me, so where would
be an appropriate place to call qspan_init and pci_scanner from? I
understand it should happen before the kernel loads, is it something
that would make sense to put in embed_config.c? Is there a more
appropriate place to put it? I can't find where (or if) it happens for
the mbx board.
Thanks!
Steve
--
-------------------------------------------------------
Steven K. Rossi srossi@ccrl.mot.com
Staff Engineer
Multimedia Communications Research Laboratory
Motorola Labs
-------------------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-20 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-20 15:57 Question on QSPAN Driver Steve Rossi
2000-03-20 17:31 ` Dan Malek
2000-03-20 19:44 ` Steve Rossi [this message]
2000-03-20 20:03 ` Dan Malek
2000-03-21 2:07 ` Jason Wohlgemuth
2000-03-21 3:07 ` Dan Malek
2000-03-22 1:35 ` Does mpc8xx-2.2.13 support "Enable loadable module support"? dony
2000-03-22 1:54 ` Joe Green
2000-03-22 3:10 ` dony
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=38D67FA3.D00A5110@ccrl.mot.com \
--to=srossi@ccrl.mot.com \
--cc=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.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).