Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Daniel Laird <daniel.j.laird@nxp.com>, linux-mips@linux-mips.org
Subject: Re: PNX8550 Broken on Linux 2.6.24 - Interrupt issues?
Date: Fri, 29 Feb 2008 18:41:44 +0300	[thread overview]
Message-ID: <47C827B8.5050209@ru.mvista.com> (raw)
In-Reply-To: <20080228222638.GB25013@linux-mips.org>

Hello.

Ralf Baechle wrote:

>>I have been happily using Linux 2.6.22.1 for ages on PNX8550 (STB810).
>> I have recently decided to step up and move onto Linux 2.6.24 series.
>>However I am not getting very far. :-(

    Heh, Daniel, you're not alone -- the Alchemy code got much more breakage 
before 2.6.24... :-)

>>The board crashes as soon as local_irq_enable is called in main.c

>>I was wondering if anyone out there might also be running on an
>>STB810/JBS PNX8550 based system and have any ideas as to why I am
>>crashing.
>>I know that PNX8550 does not enable the R4K Clock source stuff as the
>>chip is a bit 'special' and requires the two timers to be used instead
>>of one.

> csrc-r4k.c and cevt-r4k.c assume a standard compliant R4000-style
> c0_count and c0_compare register.  The PNX chips violate the expected
> behaviour badly so can't use these functions.

> But that's not very much of a problem.  The timer code is module and
> it is easy to write something like csrc-pnx.c and cevt-pnx.c to drive
> a PNX style count/compare timer.

    The PNX counter 0 can still be used as the standards clocksource with some 
ad-hockery (setting comparator to all ones and hooking the interrupt to clear 
it) but Vitaly went another way using counter 1 for clocksource, and counter 0 
as clockevent...

> Will look over the code to see if I can spot what crashes the PNXes.

>   Ralf

WBR, Sergei

  reply	other threads:[~2008-02-29 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 12:57 PNX8550 Broken on Linux 2.6.24 - Interrupt issues? Daniel Laird
2008-02-28 22:26 ` Ralf Baechle
2008-02-29 15:41   ` Sergei Shtylyov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-28 13:05 Nico Coesel
2008-02-28 13:05 ` Nico Coesel

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=47C827B8.5050209@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=daniel.j.laird@nxp.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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