netdev - Re: remove special ioctl from hso driver, replace by rfkill

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] [day] [month] [year] [list]

Date:	Mon, 21 Apr 2008 11:47:20 +0300
From:	Paulius Zaleckas <paulius.zaleckas@...tonika.lt>
To:	netdev@...r.kernel.org
Cc:	linux-usb@...r.kernel.org
Subject:  Re: remove special ioctl from hso driver, replace by rfkill

Greg KH wrote:
> On Fri, Apr 18, 2008 at 04:56:27PM +0300, Paulius Zaleckas wrote:
>> Oliver Neukum wrote:
>>> Hi,
>>> could you test this patch?
>>> It does away with the one off serial ioctl replacing it with a standard
>>> mechanism.
>>> 	Regards
>>> 		Oliver
>> I have tested rfkill and it realy works, but there is two problems:
>>
>> - LED on the device doesn't indicate rf state... Maybe Filip knows
>>   some usb command to control it?
>>
>> - driver creates multiple rfkill entries on sysfs... This is because
>>   option device has multi endpoints (probe is called twice with GTM380):
> 
> You mean "multiple interfaces" :)

Yes, I think I meant it :)

> And that's correct, for this device, that is the way it was created, so
> either rfkill entry should work to shut off the radio...

Yes, both of them work, but there is a problem...
If you change state for one them, then another one remains not updated.
Also it doesn't make sense to have two rfkill entries for one device.
Maybe it should be created only with network device?

Paulius

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