All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: Kevin Hilman <khilman@mvista.com>
Cc: "linux-omap-open-source@linux.omap.com"
	<linux-omap-open-source@linux.omap.com>
Subject: Re: CONFIG_PREEMPT_RT patch on Apollon (OMAP2)
Date: Tue, 28 Nov 2006 08:09:08 +0000 (GMT)	[thread overview]
Message-ID: <5544219.568381164701467419.JavaMail.weblogic@ep_ml19> (raw)

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

Actually I used the 32K timer.

I tested it with fsstress on JFFS2 filesystem.


diff --git a/arch/arm/plat-omap/Kconfig b/arch/arm/plat-omap/Kconfig
index f0ce772..5cccb0c 100644
--- a/arch/arm/plat-omap/Kconfig
+++ b/arch/arm/plat-omap/Kconfig
@@ -11,9 +11,11 @@ choice

 config ARCH_OMAP1
        bool "TI OMAP1"
+       select GENERIC_TIME

 config ARCH_OMAP2
        bool "TI OMAP2"
+       select GENERIC_TIME if OMAP_32K_TIMER

 endchoice

Thank you,
Kyungmin Park



------- Original Message -------
Sender : Kevin Hilman<khilman@mvista.com> 
Date   : 2006-11-28 16:08
Title  : Re: CONFIG_PREEMPT_RT patch on Apollon (OMAP2)

Dirk Behme wrote:
> Kyungmin Park wrote:
>> 2. Too many loads???
>>   - After booting. I think the system is too slow. and also it's
>> unstable. After some opeartions. it's hang.
> 
> Two additional things:
> 
> - Do you converted OMAP2 timer to clocksource as well (timer-gp.c)? I
> think our clocksource patch only covers OMAP1 (Kevin?).

Correct, only OMAP1 clocksource/clockevent done so far.

Kevin



[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2006-11-28  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28  8:09 Kyungmin Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-27  6:59 CONFIG_PREEMPT_RT patch on Apollon (OMAP2) Kyungmin Park
2006-11-27 19:09 ` Dirk Behme
2006-11-30 21:35   ` David Brownell
2006-11-28  6:14 ` Dirk Behme
2006-11-28  7:08   ` Kevin Hilman

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=5544219.568381164701467419.JavaMail.weblogic@ep_ml19 \
    --to=kyungmin.park@samsung.com \
    --cc=khilman@mvista.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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.