From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Problem when testing current git on sh3 + hp6xx
Date: Wed, 24 Feb 2010 01:03:09 +0000 [thread overview]
Message-ID: <20100224010309.GB17581@linux-sh.org> (raw)
In-Reply-To: <20100223025042.GA28763@rafazurita.homelinux.net>
On Tue, Feb 23, 2010 at 07:38:03PM -0300, Rafael Ignacio Zurita wrote:
> On Tue, Feb 23, 2010 at 12:51:09PM +0900, Paul Mundt wrote:
> > Based on this it would seem that you are entering the kernel with pending
> > timer IRQs and are racing against the clockevent setup, as no one has set
> > up the event handler yet. Try this:
>
> After to apply your patch it looks a lot better. The log :
>
> Calibrating delay loop (skipped)... 22.11 BogoMIPS PRESET (lpjD220)
It would seem that the clock framework still needs a bit of work for this
CPU..
> HD64461 configured at 0xb0000000 on irq 36(mapped into 64 to 79)
> HD64461: enabling PCMCIA devices
[snip]
> scsi0 : pata_platform
> ata1: PATA max PIO0 mmio cmd 0x150001f0 ctl 0x150001fe irq 77
Good to see that sparseirq works as advertized here too.
> If your patch is applied then I need to check why X does not run,
> but that is another story.
> If your patch is not going to mainline, then please, let me know
> what should be done to continue fixing the original issue.
>
I'll push them out today and add your Tested-by. Thanks for testing!
prev parent reply other threads:[~2010-02-24 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 2:50 Problem when testing current git on sh3 + hp6xx Rafael Ignacio Zurita
2010-02-23 3:51 ` Paul Mundt
2010-02-23 22:38 ` Rafael Ignacio Zurita
2010-02-24 1:03 ` Paul Mundt [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=20100224010309.GB17581@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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 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.