From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Galea <michaelgalea@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] How can I make Xenomai share a mii bus with the kernel?
Date: Thu, 03 Jul 2008 17:25:59 +0200 [thread overview]
Message-ID: <486CEF87.6060504@domain.hid> (raw)
In-Reply-To: <486CE4C5.8050309@domain.hid>
Michael Galea wrote:
> I wonder if someone can suggest an approach to the following problem.
>
> We need to use xenomai to manage devices on the mii bus. The mii bus
> has PHYs managed by linux. What is the best way of providing access to
> both linux and xenomai?
>
> I know that before xenomai "loads", I can simply access the mii bus from
> linux. But after xenomai loads, is the right answer to make the linux
> function that reads the phy migrate into the xenomai domain and contend
> for the bus there?
What protects this access to the bus, is this a mutex or a spinlock ? If
a spinlock, then simply make it an ipipe_spinlock, it will provide
mutual exclusion between all domains.
I do not think it can be a mutex anyway, since it may certainly possible
for a driver to have a function that reads the mii status in a timer
handler to maintain the IFF_RUNNING bit state of the ethernet interface.
--
Gilles.
next prev parent reply other threads:[~2008-07-03 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 14:40 [Xenomai-help] How can I make Xenomai share a mii bus with the kernel? Michael Galea
2008-07-03 15:25 ` Gilles Chanteperdrix [this message]
2008-07-03 15:35 ` Philippe Gerum
2008-07-03 15:38 ` Gilles Chanteperdrix
2008-07-03 15:45 ` Philippe Gerum
2008-07-03 15:52 ` Gilles Chanteperdrix
2008-07-03 20:32 ` Michael Galea
2008-07-03 20:34 ` Gilles Chanteperdrix
2008-07-03 15:41 ` Michael Galea
2008-07-03 15:43 ` Gilles Chanteperdrix
2008-07-03 15:26 ` Philippe Gerum
2008-07-03 20:15 ` Michael Galea
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=486CEF87.6060504@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=michaelgalea@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.