From: Daniele Nicolodi <daniele@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-core] Analogy regressions in xenomai 2.5.5.1
Date: Tue, 12 Oct 2010 10:44:34 +0200 [thread overview]
Message-ID: <4CB41FF2.9030602@domain.hid> (raw)
Hello, I just installed xenomai 2.5.5 on a 2.6.35.7 kernel and I'm
noticing serious regressions on analogy basic features:
1. Buffer management is badly broken. It is not possible to run any
acquisition command that wraps around in the ring buffer. That can be
simply reproduced with:
cmd_read -v d analogy0 -s 0 -S 0
after a while it will fail with: "cmd_read: a4l_read failed (ret=-32)".
In dmesg the driver reports: "Analogy: MITE: DME overwrite of free area".
2. Buffer is kept memory mapped after the mapping process dies. If a
process mapping a device buffer dies before un-mapping the buffer, it is
not possible to reconfigure the bnuffer. a4l_set_bufsize fails with
error code 32 and dmesg read "Analogy: a4l_ioctl_bufcfg: please unmap
before configuring buffer". Sinche the mapping process died I do not
know how to do this.
When I proposed some easy changes to the analogy API, to make it much
less confusing with trivial changes, Alexis expressed concerns about API
stability. What about functional stability? I think the reported ones
are major problems easily catch with simple pre-release tests...
Cheers,
Daniele
next reply other threads:[~2010-10-12 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 8:44 Daniele Nicolodi [this message]
2010-10-12 8:56 ` [Xenomai-core] Analogy regressions in xenomai 2.5.5.1 Philippe Gerum
2010-10-12 9:45 ` Daniele Nicolodi
2010-10-12 9:48 ` Gilles Chanteperdrix
2010-10-13 6:31 ` Alexis Berlemont
2010-10-13 15:10 ` Daniele Nicolodi
2010-10-15 9:16 ` Daniele Nicolodi
2010-10-15 10:15 ` Alexis Berlemont
2010-10-15 10:34 ` Daniele Nicolodi
2010-10-17 21:35 ` Alexis Berlemont
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=4CB41FF2.9030602@domain.hid \
--to=daniele@domain.hid \
--cc=xenomai@xenomai.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 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.