From: Greg Ungerer <gerg@snapgear.com>
To: Jon Ringle <jringle@vertical.com>
Cc: Adrian Cox <adrian@humboldt.co.uk>,
"linux-os (Dick Johnson)" <linux-os@analogic.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux running on a PCI Option device?
Date: Mon, 06 Mar 2006 14:03:00 +1000 [thread overview]
Message-ID: <440BB474.8000500@snapgear.com> (raw)
In-Reply-To: <200603031331.16849.jringle@vertical.com>
Hi Jon,
Jon Ringle wrote:
> On Friday 03 March 2006 09:40 am, Adrian Cox wrote:
>
>>Based on only a quick look at the code: if the Windows host is present,
>>don't call pci_common_init() in ixdp425_pci_init().
>
>
> Doing this will prevent the code in ixp4xx_pci_preinit() from executing which
> handles some initialization for both PCI host and option modes. Should I go
> ahead and explicitly call ixp4xx_pci_preinit() from ixdp425_pci_init() if in
> PCI option mode?
The older 2.4 kernel code for the IXP425 support pretty much did it
this way (which is what makes it look like it supports the device
in option mode).
Code snippet from ixp425_pci_init() in arch/arm/mach-ixp425/ixp425-pci.c
(from patches for 2.4 kernels to support ixp425):
...
if (ixp425_pci_is_host())
{
local_write_config_word(PCI_COMMAND, PCI_COMMAND_MASTER |
PCI_COMMAND_MEMORY);
DBG("allocating hose\n");
hose = pcibios_alloc_controller();
if (!hose)
panic("Could not allocate PCI hose");
hose->first_busno = 0;
hose->last_busno = 0;
hose->io_space.start = 0;
hose->io_space.end = 0xffffffff;
hose->mem_space.start = 0x48000000;
hose->mem_space.end = 0x4bffffff;
/* autoconfig the bus */ DBG("AUTOCONFIG\n");
hose->last_busno = pciauto_bus_scan(hose, 0);
/* scan the bus */
DBG("SCANNING THE BUS\n");
pci_scan_bus(0, &ixp425_ops, sysdata);
}
Pretty much the rest of the PCI init is the same, it just
doesn't do the bus scan.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com
SnapGear -- a Secure Computing Company PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2006-03-06 4:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 6:43 Linux running on a PCI Option device? Greg Ungerer
2006-02-09 16:31 ` Jon Ringle
2006-02-14 5:03 ` Greg Ungerer
2006-02-28 20:35 ` Jon Ringle
2006-02-28 21:13 ` linux-os (Dick Johnson)
2006-03-01 11:47 ` Krzysztof Halasa
2006-03-02 22:07 ` Jon Ringle
2006-03-03 9:13 ` Adrian Cox
2006-03-03 14:09 ` Jon Ringle
2006-03-03 14:40 ` Adrian Cox
2006-03-03 18:31 ` Jon Ringle
2006-03-04 16:32 ` Adrian Cox
2006-03-06 4:03 ` Greg Ungerer [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-09 6:06 Jon Ringle
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=440BB474.8000500@snapgear.com \
--to=gerg@snapgear.com \
--cc=adrian@humboldt.co.uk \
--cc=jringle@vertical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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