From: Eugene Surovegin <ebs@ebshome.net>
To: MERRITT Nigel <Nigel.Merritt@tenix.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Interrupts on PPC 405Gr
Date: Thu, 5 Feb 2004 19:52:14 -0800 [thread overview]
Message-ID: <20040206035214.GC6578@gate.ebshome.net> (raw)
In-Reply-To: <200402060337.OAA03632@sprint.tenix.com>
On Fri, Feb 06, 2004 at 02:37:18PM +1100, MERRITT Nigel wrote:
>
> The kernel is 2.4.18 from Timesys.
Well, maybe you should ask them? I wasn't able to find any
downloadable PPC 4xx BSPs on Timesys web site.
> We have a logic analyser hooked up so we know for certain that the
> signal is being generated on the correct line and is entering the UIC.
OK
> CPC0_CR0 is being set using the (probably very wrong) code:
>
> register_val = mfdcr(CPC0_CR0); // Read value from the register.
>
> // Set to 0.
> register_val = register_val & MASK_BIT_NOT_6;
> register_val = register_val & MASK_BIT_NOT_7;
[snip]
I'd prefer real (hex) values, even better, just print them out after
you set them, i.e.
printk("0x%08x\n", mfcdr(CPC0_CR0));
I have no idea how you defined all these macros.
> Polarity and trigger settings are being set in a similar manner, i.e:
[snip]
> Again, how do these get set if not by adjusting the registers?
Well, official PPC kernels have a sane way to do this, look for
ibm4xxPIC_InitSenses in arch/ppc/platforms. Not sure whether Timesys
kernel has it.
And this kind of stuff (e.g. CPC0_CR0, polarity/trigerring settings)
is usually done in firmware not in the kernel.
Try official PPC kernel trees, at least they are known to work on
405 hardware. Maybe you problems are Timesys kernel specific.
Eugene.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-06 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 3:37 Interrupts on PPC 405Gr MERRITT Nigel
2004-02-06 3:52 ` Eugene Surovegin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 6:45 MERRITT Nigel
2004-02-06 6:43 ` Eugene Surovegin
2004-02-06 2:47 MERRITT Nigel
2004-02-06 3:08 ` Eugene Surovegin
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=20040206035214.GC6578@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=Nigel.Merritt@tenix.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).