From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] [PATCH 0/5] Xenomai patch queue
Date: Tue, 20 Nov 2007 19:10:45 +0100 [thread overview]
Message-ID: <47432325.5010509@domain.hid> (raw)
In-Reply-To: <4738D9D1.5090802@domain.hid>
Jan Kiszka wrote:
> Hi,
>
> while the syscall tracing thing still puzzles me, I was now at least
> able to check that my patches do what they are supposed to. So here
> comes a flush of (most of) the stuff that piled up on my side, fixing or
> enhancing the following aspects:
>
> - x86 hal refactoring (-v2) - I decided to base my work on this because
> it shakes the code anyway and also happens to touch hal stuff, thus
> benefits from the unified version.
>
> - get timer frequency from ipipe (thus Linux) instead of relying on
> home-brewed estimations (fixes inaccurate APIC frequency)
>
> - report configured timer and clock device via /proc/xenomai/timer
>
> - cleanup tickdev emulation (related to I-pipe refactorings)
>
Looks good. I will not even make a fuss about the ipipe_request_tickdev
API breakage (surprise, surprise...), since we should be able to avoid
the nuisance with proper detection of new I-pipe patches. To this end,
I'm going to introduce a known feature list as defines in new Adeos
releases, so that downstream may rely on their presence for proper
feature selection. This should hopefully help normalizing such kind of
detection code.
Will merge asap, to be included in -rc7 since most of the patch is about
moving code around to streamline the x86* HAL support.
Thanks,
--
Philippe.
prev parent reply other threads:[~2007-11-20 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 22:55 [Xenomai-core] [PATCH 0/5] Xenomai patch queue Jan Kiszka
2007-11-20 18:10 ` Philippe Gerum [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=47432325.5010509@domain.hid \
--to=rpm@xenomai.org \
--cc=Xenomai-core@domain.hid \
--cc=jan.kiszka@domain.hid \
/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.