From: Adrian Cox <adrian@humboldt.co.uk>
To: Jon Ringle <jringle@vertical.com>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
Greg Ungerer <gerg@snapgear.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux running on a PCI Option device?
Date: Fri, 03 Mar 2006 14:40:43 +0000 [thread overview]
Message-ID: <1141396843.8912.49.camel@localhost.localdomain> (raw)
In-Reply-To: <200603030909.28640.jringle@vertical.com>
On Fri, 2006-03-03 at 09:09 -0500, Jon Ringle wrote:
> On Friday 03 March 2006 04:13 am, Adrian Cox wrote:
> > If you're running on a PCI option device (unless using a 21555
> > non-transparent bridge), you need to disable CONFIG_PCI and write your
> > own driver for the PCI option device functionality.
>
> Another requirement that I have that makes it difficult for me to disable
> CONFIG_PCI is that the hardware component that is running Windows (and
> therefore the PCI host) is optional hardware. If the Windows part is not
> present, then the IXP will be configured (via hardware means) as a PCI host.
> So, I need to detect at run time whether the IXP is in PCI option or PCI host
> mode. If it is in PCI host mode then the code encapuslated by CONFIG_PCI must
> be available.
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(). You then need to
write the entire CONFIG_PCI_GADGET code, and ensure that you only enable
it if the Windows host is present.
The greater problem is that these changes may work all the way up into
your application. If the Windows host is present, then you need its
cooperation to find other devices on the PCI bus.
--
Adrian Cox <adrian@humboldt.co.uk>
next prev parent reply other threads:[~2006-03-03 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 6:43 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 [this message]
2006-03-03 18:31 ` Jon Ringle
2006-03-04 16:32 ` Adrian Cox
2006-03-06 4:03 ` Greg Ungerer
-- 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=1141396843.8912.49.camel@localhost.localdomain \
--to=adrian@humboldt.co.uk \
--cc=gerg@snapgear.com \
--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
Powered by JetHome