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 09:13:07 +0000 [thread overview]
Message-ID: <1141377188.8912.25.camel@localhost.localdomain> (raw)
In-Reply-To: <200603021707.01190.jringle@vertical.com>
On Thu, 2006-03-02 at 17:07 -0500, Jon Ringle wrote:
> As it turns out, Linux completes it's bootup before Windows bootup even
> begins, and it seems that Linux changes the configuration of the various
> other PCI devices that happen to be on the system as well. I need to get
> Linux to leave the configuration of other PCI devices it finds alone. It
> should only mess with it's own configuration. Why should Linux need to change
> the configuration of other PCI devices when it is fulfilling the role of a
> PCI device itself?
Have you disabled CONFIG_PCI?
CONFIG_PCI is the configuration option for a PCI host, just as
CONFIG_USB is the configuration option for a USB host. Linux contains
code for CONFIG_USB_GADGET, but what you need is the non-existent
CONFIG_PCI_GADGET.
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.
--
Adrian Cox <adrian@humboldt.co.uk>
next prev parent reply other threads:[~2006-03-03 9:13 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 [this message]
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
-- 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=1141377188.8912.25.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