From: Dirk Behme <dirk.behme@googlemail.com>
To: kyungmin.park@samsung.com, OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: CONFIG_PREEMPT_RT patch on Apollon (OMAP2)
Date: Mon, 27 Nov 2006 20:09:54 +0100 [thread overview]
Message-ID: <456B3802.1000101@gmail.com> (raw)
In-Reply-To: <11115895.486281164610759448.JavaMail.weblogic@ep_ml20>
Kyungmin Park wrote:
> As you mentioned, I tried to use CONFIG_PREEMPT_RT patch.
Great!
> But there's some issues.
Yep, CONFIG_PREEMPT_RT still looks experimental on our
platform. Hopefully we contribute to improvement by testing it.
> 1. ethernet flags
> - After change from IRQF_RISING to IRQF_HIGH in recent OMAP2 patch. it occurs the GPIO bug message in line 1005.
> So I reverted IRQF_RISING as before. then it's working.
Maybe David has an idea here? [1]
Regarding ethernet I'm unsure. On OSK/OMAP1 my testcase is
playing MP3 over NFS. While writing my previous mail, I
never reached the end of MP3 because of NFS timeouts and
connection losses.
Today, I tried again to get the exact error message and now
no NFS issues any more. MP3 properly finishes.
> 2. Too many loads???
> - After booting. I think the system is too slow. and also it's unstable. After some opeartions. it's hang.
Can't say this for OSK, feeling is same speed or even
faster. For me, ALSA was unstable because I missed to
convert some spinlocks to raw_spinlocks. Maybe you should
check if you found all?
What's your testcase? For which operations does it hang?
> 3. ARMv6 support
> - current cmpxchg support for under ARMv6 only.
Don't know anything about ARMv6.
Cheers
Dirk
[1]
http://linux.omap.com/pipermail/linux-omap-open-source/2006-November/008270.html
next prev parent reply other threads:[~2006-11-27 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 6:59 CONFIG_PREEMPT_RT patch on Apollon (OMAP2) Kyungmin Park
2006-11-27 19:09 ` Dirk Behme [this message]
2006-11-30 21:35 ` David Brownell
2006-11-28 6:14 ` Dirk Behme
2006-11-28 7:08 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2006-11-28 8:09 Kyungmin Park
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=456B3802.1000101@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=kyungmin.park@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox