From: Anders Blomdell <anders.blomdell@domain.hid>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Analogy/mite
Date: Fri, 09 Dec 2011 21:10:18 +0100 [thread overview]
Message-ID: <4EE26B2A.1040702@domain.hid> (raw)
In-Reply-To: <4EE22E83.6050406@domain.hid>
On 12/09/2011 04:51 PM, Anders Blomdell wrote:
> On 12/09/2011 02:35 PM, Anders Blomdell wrote:
>> On 11/30/2011 07:03 PM, Anders Blomdell wrote:
>>> Hi, just found that
>>>
>>> echo 0000:06:01.0 > /sys/bus/pci/drivers/analogy_mite/unbind
>>>
>>> does not do the same thing as
>>>
>>> analogy_config -r analogyN
>>>
>>> in fact it leaves the system in a state where using the driver results
>>> in a kernel OOPS.
>>>
>>> Will try to look into it further tomorrow...
>> Well, took quite some time to track down the 'analogy_config -r' bug
>> (which was responsible for the kernel OOPS [i.e. after fixing it I have
>> not got any OOPSes]).
>>
>> So back to the original problem, does anybody foresee that a call to
>> a4l_ioctl_devcfg(cxt, NULL) from the mite driver would give any problems
>> (apart from getting the context pointer from the data structures the
>> mite driver has handy)? It is probably not kosher to do ioctl on a
>> driver that is not open, but...
> Attached is a hack (as can be gleaned from the EXPORT_SYMBOL_GPL), if
> the basic assumption that it's ok to do a a4l_ioctl_devcfg(...) during
> unbind, I could rewrite the logic to pass down a pointer to
> a4l_ioctl_devcfg to avoid this.
Sloppy me, should of course be:
>+ if (mite->a4ldev) {
if (mite->a4ldev && mite->a4ldev->cxt) {
>+ a4l_ioctl_devcfg(mite->a4ldev->cxt, NULL);
>+ }
prev parent reply other threads:[~2011-12-09 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 18:03 [Xenomai-core] Analogy/mite Anders Blomdell
2011-12-01 15:03 ` Anders Blomdell
2011-12-06 22:47 ` Alexis Berlemont
2011-12-07 7:58 ` Anders Blomdell
2011-12-08 16:19 ` Anders Blomdell
2011-12-09 10:27 ` Anders Blomdell
2011-12-09 13:35 ` Anders Blomdell
2011-12-09 15:51 ` Anders Blomdell
2011-12-09 20:10 ` Anders Blomdell [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=4EE26B2A.1040702@domain.hid \
--to=anders.blomdell@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.