lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140716204004.GA31349@kroah.com>
Date:	Wed, 16 Jul 2014 13:40:04 -0700
From:	Greg KH <greg@...ah.com>
To:	Michalis Pappas <mpappas@...tmail.fm>
Cc:	devel@...verdev.osuosl.org, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org, inaky@...ux.intel.com
Subject: Re: How to replace control code in gdm72xx?

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ