From: David Hawkins <dwh@ovro•caltech.edu>
To: "Travis B. Sawyer" <tsawyer+linuxppc@sandburst•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Artesyn Processor PMC 'Host Bridge' has no IRQ assigned?
Date: Tue, 07 Feb 2006 15:03:33 -0800 [thread overview]
Message-ID: <43E92745.1080407@ovro.caltech.edu> (raw)
In-Reply-To: <43E92584.1000007@sandburst.com>
Hi Travis,
> It's been a couple of years since I've had to mess with the
> ArtPrPMC board. There is, IIRC, there is a doorbell register
> in the CPC700, but I don't have the spec handy. My last
> use of the prpmc was with vxworks and shared memory
> messaging using a doorbell.
Yeah, thats pretty much the 'way of PCI', so I was surprized
not to see the IRQ line assigned from the x86 host-side.
> Umm... I recall stating the XPEDITE1000 from X-ES was
> supported by u-boot (I'll have to submit another patch to
> Wolfgang as they(XES) changed some stuff wrt flash write
> protect, I've also moved the env from the cramped i2c eeprom
> (bad) to the intel flash).
Oh, perhaps the comment was that you had used the board then :)
> I'd have to check the u-boot source for PrPMC support, as I
> haven't run u-boot on it.
No sweat, if I want to put U-Boot on it, then I'll just have to
port it :) Since the Artesyn bootloader can tftp etc, I'll
figure out first how to get Linux booted.
I just booted up the second board, and it did not get
an IRQ either. I'll dig into the CPC700 manual, its likely
a boot-time enable.
Thanks for the feedback!
Dave
prev parent reply other threads:[~2006-02-07 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 1:40 Suggestions for a PPC440 board? David Hawkins
2006-01-13 13:26 ` Travis B. Sawyer
2006-01-13 16:51 ` David Hawkins
2006-01-13 17:02 ` Artesyn PM/PPC 750 U-Boot/Linux support? Datasheet? David Hawkins
2006-01-13 17:28 ` David Hawkins
2006-02-07 22:27 ` Artesyn Processor PMC 'Host Bridge' has no IRQ assigned? David Hawkins
2006-02-07 22:56 ` Travis B. Sawyer
2006-02-07 23:03 ` David Hawkins [this message]
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=43E92745.1080407@ovro.caltech.edu \
--to=dwh@ovro$(echo .)caltech.edu \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=tsawyer+linuxppc@sandburst$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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