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 <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
