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: Sat, 04 Mar 2006 16:32:27 +0000 [thread overview]
Message-ID: <1141489948.9197.1.camel@localhost.localdomain> (raw)
In-Reply-To: <200603031331.16849.jringle@vertical.com>
On Fri, 2006-03-03 at 13:31 -0500, 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?
At this point I have to give up - I'm not an ixp4xx expert. While I have
developed a PCI option device under Linux, it was a PowerPC with a PLX
bridge and some custom logic.
--
Adrian Cox <adrian@humboldt.co.uk>
next prev parent reply other threads:[~2006-03-04 16:32 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 [this message]
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=1141489948.9197.1.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.