Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Manuel Lauss <manuel.lauss@fh-hagenberg.at>, linux-mips@linux-mips.org
Subject: Re: [PATCH 0/2] Alchemy: fix interrupt routing
Date: Wed, 05 Dec 2007 21:57:24 +0300	[thread overview]
Message-ID: <4756F494.8090207@ru.mvista.com> (raw)
In-Reply-To: <20071205182353.GC10697@linux-mips.org>

Ralf Baechle wrote:

>>Thanks a billion!
>>Finally I can boot linux-2.6.24-rc on my Au1200 again!

> And with a bit of luck Alchemy will now support tickless, too.

    It works:

Timer Stats Version: v0.2
Sample period: 8.024 s
     8,     1 swapper          __netdev_watchdog_up (dev_watchdog)
     8,     1 swapper          phy_connect (phy_timer)
     8,     1 swapper          phy_connect (phy_timer)
     7,     0 swapper          receive_chars (delayed_work_timer_fn)
     1,     1 swapper          cache_register (delayed_work_timer_fn)
     1,     1 swapper          neigh_table_init_no_netlink (neigh_periodic_timer)
     4,     1 swapper          queue_delayed_work_on (delayed_work_timer_fn)
     2,   866 mvltd            schedule_timeout (process_timeout)
     1,     0 swapper          page_writeback_init (wb_timer_fn)
     1,     1 init             schedule_timeout (process_timeout)
41 total events, 5.109 events/sec

>   Ralf

WBR, Sergei

  parent reply	other threads:[~2007-12-05 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 16:08 [PATCH 0/2] Alchemy: fix interrupt routing Sergei Shtylyov
2007-12-05 16:39 ` Manuel Lauss
2007-12-05 18:23   ` Ralf Baechle
2007-12-05 18:29     ` Sergei Shtylyov
2007-12-05 18:57     ` Sergei Shtylyov [this message]
2007-12-05 19:12       ` Ralf Baechle
2007-12-05 19:22         ` Sergei Shtylyov

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=4756F494.8090207@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=manuel.lauss@fh-hagenberg.at \
    --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