Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Laird <daniel.j.laird@nxp.com>
Cc: linux-mips@linux-mips.org
Subject: Re: PNX8550 Broken on Linux 2.6.24 - Interrupt issues?
Date: Thu, 28 Feb 2008 22:26:38 +0000	[thread overview]
Message-ID: <20080228222638.GB25013@linux-mips.org> (raw)
In-Reply-To: <64660ef00802280457i3eef020chd70f85c011c5a770@mail.gmail.com>

On Thu, Feb 28, 2008 at 12:57:47PM +0000, Daniel Laird 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. :-(
> It seems that all the clock stuff has changed again (since 2.6.22.1)
> and this is causing issues.

Yes, it's a bit special and I don't have any possibility to test the
PNX code so I left it mostly untouched when rewriting the timer code.
Sorry about that but eventually I had to go ahead.  Vitaly Wool
eventually submitted a few patches to fix things but as your testing
seems to show that wasn't quite enough.  That far about the history
of the changes.

> 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.

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

  Ralf

  reply	other threads:[~2008-02-28 22:26 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 [this message]
2008-02-29 15:41   ` Sergei Shtylyov
  -- 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=20080228222638.GB25013@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=daniel.j.laird@nxp.com \
    --cc=linux-mips@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