From: Greg Ungerer <gerg@snapgear.com>
To: Jon Ringle <jringle@vertical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux running on a PCI Option device?
Date: Tue, 14 Feb 2006 15:03:00 +1000 [thread overview]
Message-ID: <43F16484.2080800@snapgear.com> (raw)
In-Reply-To: <200602091131.12535.jringle@vertical.com>
Hi Jon,
Jon Ringle wrote:
> On Thursday 09 February 2006 01:43 am, Greg Ungerer wrote:
>>Jon Ringle wrote:
>>>I am working on a new board that will have Linux running on an xscale
>>>processor. This board will be a PCI Option device. I currently have a
>>>IXDP465 eval board which has a PCI Option connector that I will use for
>>>prototyping. From what I can tell so far, Linux wants to scan the PCI bus
>>>for devices as if it is the PCI host. Is there any provision in Linux so
>>>that it can take on the role of a PCI option rather than a PCI host?
>>
>>Have a look at the code in arch/arm/mach-ixp4xx/common-pci.c, in
>>the function ixp4xx_pci_preinit().
>>
>>It does a check on whether the PCI bus is configured as HOST or not.
>>I don't know if that code support is enough for it all to work right
>>though (I certainly haven't tried it on either the 425 or 465...)
>
>
> Something that I don't quite understand is how I'm supposed to make vendor Id
> information available to the PCI host. Any ideas there?
No, sorry, no idea. I haven't looked at it in that much detail.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com
SnapGear -- a CyberGuard 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-02-14 5:02 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 [this message]
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
-- 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=43F16484.2080800@snapgear.com \
--to=gerg@snapgear.com \
--cc=jringle@vertical.com \
--cc=linux-kernel@vger.kernel.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