From: Wolfgang Grandegger <wg@grandegger.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Status of -rt for linux-2.6.20/arch/powerpc
Date: Sun, 11 Feb 2007 13:39:44 +0100 [thread overview]
Message-ID: <45CF0E90.2080806@grandegger.com> (raw)
In-Reply-To: <20070211112933.GN29553@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
Hi Robert,
Robert Schwebel wrote:
> Hello Wolfgang,
>
> On Sun, Feb 11, 2007 at 12:10:15PM +0100, Wolfgang Grandegger wrote:
>> what is the status of the Preemptive Kernel and the High Resolution
>> Timers for Linux 2.6.20 for PowerPC (arch/powerpc or arch/ppc)?
>>
>> I realized build problems when trying to get it working for my Lite5200
>> (MPC5200) board with patch-2-6-20-rt5. The patch seems to contain
>> reminders of merge conflicts, e.g.:
>>
>> +++ linux/include/asm-powerpc/hw_irq.h
>> ...
>> +<<<<<<< delete extern unsigned long local_get_flags(void);
>> +<<<<<<< delete extern unsigned long local_irq_disable(void);
>>
>> and the make fails in arch/powerpc/kernel/time.c as well (see attachment).
>
> We have 2.6.20-rt3 running on the phyCORE-MPC5200B, so that one should
> work and the merge problems did probably come in later (don't have the
> time to look right now because of the Embedded World activities for next
> week).
As I see it, 2.6.20-rt3 has the same issues (have now attached the
missing make output). I fixed them manually and are now able to boot and
run the 2.6.20-rt5 on my Icecube board. Nevertheless, cyclictest returns
high values of around 8000-10000 (8-10ms). The fact that the unknown
field 'is_continuous' in arch/powerpc/kernel/time.c is still present
gives me the impression, that the code in there is not up-to-date. See
you next week on the Embedded World.
Thanks.
Wolfgang.
[-- Attachment #2: make.log --]
[-- Type: text/x-log, Size: 701 bytes --]
CC arch/powerpc/kernel/time.o
In file included from arch/powerpc/kernel/time.c:924:
include/linux/clocksource.h: In function 'ns2cyc':
include/linux/clocksource.h:174: warning: comparison of distinct pointer types lacks a cast
include/linux/clocksource.h:174: warning: right shift count >= width of type
include/linux/clocksource.h:174: warning: passing argument 1 of '__div64_32' from incompatible pointer type
arch/powerpc/kernel/time.c: At top level:
arch/powerpc/kernel/time.c:938: error: unknown field 'is_continuous' specified in initializer
make[1]: *** [arch/powerpc/kernel/time.o] Error 1
make[1]: Target `__build' not remade because of errors.
make: *** [arch/powerpc/kernel] Error 2
next prev parent reply other threads:[~2007-02-11 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 11:10 Status of -rt for linux-2.6.20/arch/powerpc Wolfgang Grandegger
2007-02-11 11:29 ` Robert Schwebel
2007-02-11 12:39 ` Wolfgang Grandegger [this message]
2007-02-11 15:57 ` Thomas Gleixner
2007-02-11 16:37 ` Wolfgang Grandegger
2007-02-11 16:39 ` Thomas Gleixner
2007-02-11 15:59 ` Robert Schwebel
2007-02-11 16:39 ` Wolfgang Grandegger
-- strict thread matches above, loose matches on Subject: below --
2007-03-06 8:02 pradyumna.sampath
[not found] <OF77E4A7D3.89DEBB42-ON65257296.002B7648-65257296.002B9889@abbasiapacific.com.sg>
2007-03-06 8:27 ` Robert Schwebel
2007-03-07 9:02 pradyumna.sampath
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=45CF0E90.2080806@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
/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.