From: vb <vb@vsbe.com>
To: LinuxPPC-Embedded <linuxppc-embedded@ozlabs.org>,
linuxppc-dev@ozlabs.org
Subject: Setting eth interface oper state from user space
Date: Mon, 30 Mar 2009 13:04:38 -0700 [thread overview]
Message-ID: <f608b67d0903301304t58028e88t6ba6d4f9b030ef88@mail.gmail.com> (raw)
I'm debugging a fairly awkward system, where the ehernet controller
and the phy device connected to the controller's mac are completely
independent. (this is in the 2.6.25 tree, btw).
The phy device interface is through SysFs attributes, there is no
interrupts, link state is polled by a user space thread.
When I try using this new ethernet interface, it's never in the
operational 'running' state, so it never gets used.
I see that many drivers use netif_carrier_on() to set oper state, but
this is invoked from the driver code in the kernel.
Is there a recommended way of controlling the interface operstate from
user space? Or maybe someone has a suggestion on how to do this in the
cleanest possible way?
As always, any hints/comments will be highly appreciated,
TIA,
Vadim
reply other threads:[~2009-03-30 20:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f608b67d0903301304t58028e88t6ba6d4f9b030ef88@mail.gmail.com \
--to=vb@vsbe.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).