From: Michalis Pappas <mpappas-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: inaky-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
Ben Chan <benchan-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: How to replace control code in gdm72xx?
Date: Wed, 16 Jul 2014 21:24:28 +0100 [thread overview]
Message-ID: <53C6DF7C.8030109@fastmail.fm> (raw)
Hi,
I'm currently working on bringing the gdm72xx WiMAX driver out of
staging. The driver currently uses two control channels:
1. The SIOCDEVPRIVATE ioctl to send and receive state messages
2. A customly defined netlink protocol for passing messages verbatim to
the device controller
AFAIK both of the above are deprecated, so I considered switching to
the interface defined in wimax.h, which defines a communication protocol
over generic netlink that replaces (2) nicely. However it is not
compatible with (1), as:
* Except from the device status, the gdm72xx driver uses two more types
of messages (connection and OMA status), which is not supported
by wimax.h.
* The gdm driver needs to be able to receive status messages from
userspace, which is not supported by wimax.h either.
I therefore consider using the wimax stack as defined in wimax.h for the
netlink part, but replacing the ioctl with a file under /sys/class/net/wm0/
My questions are whether the above location would be the right place for
that file, and, more importantly, whether this is a generally a valid
approach and not just an ugly workaround.
Thanks,
Michalis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-07-16 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 20:24 Michalis Pappas [this message]
2014-07-16 20:40 ` How to replace control code in gdm72xx? Greg KH
2014-07-17 0:59 ` Ben Chan
2014-07-25 14:10 ` Michalis Pappas
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=53C6DF7C.8030109@fastmail.fm \
--to=mpappas-97jfqw80gc6171pxa8y+qa@public.gmane.org \
--cc=benchan-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org \
--cc=inaky-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).