Re: [PATCH] toshiba_acpi: Support RFKILL hotkey scancode

In Windows disables the Wi-Fi & Bluetooth. In Linux does nothing but showing this error in dmesg about the unrecognized scancode: [230128.042047] toshiba_acpi: Unknown key 158 On Tue, Jan 14, 2014 at 4:54 PM, Matthew Garrett wrote: > On Tue, 2014-01-14 at 11:06 +0100, Unai Uribarr

[PATCH] toshiba_acpi: Support RFKILL hotkey scancode

This scancode is used in new 2013 models like Satellite P75-A7200. Signed-off-by: Unai Uribarri --- drivers/platform/x86/toshiba_acpi.c |1 + 1 file changed, 1 insertion(+) diff --git a/drivers/platform/x86/toshiba_acpi.c b/drivers/platform/x86/toshiba_acpi.c index 7fce391..5d23ca2 100644

[PATCH] toshiba_acpi: Support RFKILL hotkey scancode

This scancode is used in new 2013 models like Satellite P75-A7200. Signed-off-by: Unai Uribarri una...@gmail.com --- drivers/platform/x86/toshiba_acpi.c |1 + 1 file changed, 1 insertion(+) diff --git a/drivers/platform/x86/toshiba_acpi.c b/drivers/platform/x86/toshiba_acpi.c index 7fce391

Re: [PATCH] toshiba_acpi: Support RFKILL hotkey scancode

, Unai Uribarri wrote: This scancode is used in new 2013 models like Satellite P75-A7200. Just to check - this is generated by a key that otherwise does nothing, right? Ie, hitting the key generates the scancode but doesn't automatically change the wireless state? -- Matthew Garrett matthew.garr

Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

On vie, 2007-08-10 at 12:34 +0400, Evgeniy Polyakov wrote: > Hi Unai. > > On Thu, Aug 09, 2007 at 08:44:21PM +0200, Unai Uribarri ([EMAIL PROTECTED]) > wrote: > > There is another option: > > > > 1. Move timestampt activation to packet_set_ring(), so it's ac

Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

On vie, 2007-08-10 at 12:34 +0400, Evgeniy Polyakov wrote: Hi Unai. On Thu, Aug 09, 2007 at 08:44:21PM +0200, Unai Uribarri ([EMAIL PROTECTED]) wrote: There is another option: 1. Move timestampt activation to packet_set_ring(), so it's activated only once at setup instead of every

Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

Do not enable timestamps automatically on mmap'ed AF_PACKET sockets. --- commit d1d6e6bf196e31b6306fd0fef95f4190983c8a86 tree 22637506c0aafeabfbe05faf5352d0358c4d9460 parent 6a302358d87fedaf7bda12b8e909265ebf1ce674 author Unai Uribarri <[EMAIL PROTECTED]> Tue, 31 Jul 2007 20:38:42 +0200 com

Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

multipart format and they were removed from the list archives. I can resent them in plain text if needed. On jue, 2007-08-09 at 22:18 +0400, Evgeniy Polyakov wrote: > On Thu, Aug 09, 2007 at 08:13:54PM +0200, Unai Uribarri ([EMAIL PROTECTED]) > wrote: > > On jue, 2007-08-09 at

Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

On jue, 2007-08-09 at 18:33 +0400, Evgeniy Polyakov wrote: > On Thu, Aug 09, 2007 at 04:21:54PM +0200, Unai Uribarri ([EMAIL PROTECTED]) > wrote: > > The attached patch removes the automatic timestamp activation, that > > only mmap'ed AF_PACKET sockets perform. I known

[PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

capturing application. The attached patch removes the automatic timestamp activation, that only mmap'ed AF_PACKET sockets perform. I known it can break user applications, but I believe that it's the correct solution. I will be very pleased to receive any feedback. Signed-off-by: Unai Uribarri

[PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

capturing application. The attached patch removes the automatic timestamp activation, that only mmap'ed AF_PACKET sockets perform. I known it can break user applications, but I believe that it's the correct solution. I will be very pleased to receive any feedback. Signed-off-by: Unai Uribarri

Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

On jue, 2007-08-09 at 18:33 +0400, Evgeniy Polyakov wrote: On Thu, Aug 09, 2007 at 04:21:54PM +0200, Unai Uribarri ([EMAIL PROTECTED]) wrote: The attached patch removes the automatic timestamp activation, that only mmap'ed AF_PACKET sockets perform. I known it can break user applications

Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

multipart format and they were removed from the list archives. I can resent them in plain text if needed. On jue, 2007-08-09 at 22:18 +0400, Evgeniy Polyakov wrote: On Thu, Aug 09, 2007 at 08:13:54PM +0200, Unai Uribarri ([EMAIL PROTECTED]) wrote: On jue, 2007-08-09 at 18:33 +0400, Evgeniy

Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

Do not enable timestamps automatically on mmap'ed AF_PACKET sockets. --- commit d1d6e6bf196e31b6306fd0fef95f4190983c8a86 tree 22637506c0aafeabfbe05faf5352d0358c4d9460 parent 6a302358d87fedaf7bda12b8e909265ebf1ce674 author Unai Uribarri [EMAIL PROTECTED] Tue, 31 Jul 2007 20:38:42 +0200 committer

[PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

capturing application. The attached patch removes the automatic timestamp activation, that only mmap'ed AF_PACKET sockets perform. I known it can break user applications, but I believe that it's the correct solution. I will be very pleased to receive any feedback. Signed-off-by: Unai Uribarri

[PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets

capturing application. The attached patch removes the automatic timestamp activation, that only mmap'ed AF_PACKET sockets perform. I known it can break user applications, but I believe that it's the correct solution. I will be very pleased to receive any feedback. Signed-off-by: Unai Uribarri