All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michalis Pappas <mpappas@fastmail.fm>
Cc: devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, inaky@linux.intel.com
Subject: Re: How to replace control code in gdm72xx?
Date: Wed, 16 Jul 2014 13:40:04 -0700	[thread overview]
Message-ID: <20140716204004.GA31349@kroah.com> (raw)
In-Reply-To: <53C6DF7C.8030109@fastmail.fm>

On Wed, Jul 16, 2014 at 09:24:28PM +0100, Michalis Pappas wrote:
> 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.

What type of status messages are needed to be sent to the driver?

> 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/

Is anyone still working on wimax to even object to add new functions
like this?  :)

thanks,

greg k-h

  reply	other threads:[~2014-07-16 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 20:24 How to replace control code in gdm72xx? Michalis Pappas
2014-07-16 20:24 ` Michalis Pappas
2014-07-16 20:40 ` Greg KH [this message]
2014-07-17  0:59   ` Ben Chan
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=20140716204004.GA31349@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=inaky@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mpappas@fastmail.fm \
    --cc=netdev@vger.kernel.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.