headers
chris | 1 Jan 2011 22:44

[PATCH] Remap Eee PC touchpad toggle key to F21 used by X

From: Chris Bagwell <chris <at> cnpbagwell.com>

Currently, Eee PC have a hotkey that generates KEY_F13 but this
will soon change to KEY_TOUCHPAD_TOOGLE.  Both cases do not
work well with X.

X has defined F21 for the purpose of touchpad toggle and other
udev keymaps align with this meaning.  Patch aligns Eee PC
hotkey drivers with F21.

Tested on Eee PC 1005PE using both eeepc-wmi and eeepc-laptop driver
(with acpi_osi="!Windows 2009").

Signed-off-by: Chris Bagwell <chris <at> cnpbagwell.com>
---
 extras/keymap/95-keymap.rules |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/extras/keymap/95-keymap.rules b/extras/keymap/95-keymap.rules
index 053838d..9059a8c 100644
--- a/extras/keymap/95-keymap.rules
+++ b/extras/keymap/95-keymap.rules
 <at>  <at>  -44,6 +44,8  <at>  <at>  ENV{DMI_VENDOR}=="LENOVO*", KERNELS=="input*", ATTRS{name}=="ThinkPad Extra Butt
 ENV{DMI_VENDOR}=="LENOVO*", KERNELS=="input*", ATTRS{name}=="Lenovo ThinkPad SL Series extra
buttons", RUN+="keymap $name 0x0E bluetooth"
 ENV{DMI_VENDOR}=="ASUS*", KERNELS=="input*", ATTRS{name}=="Asus Extra Buttons",
ATTR{[dmi/id]product_name}=="W3J", RUN+="keymap $name module-asus-w3j"
 ENV{DMI_VENDOR}=="Sony*", KERNELS=="input*", ATTRS{name}=="Sony Vaio Keys", RUN+="keymap $name module-sony"
+ENV{DMI_VENDOR}=="ASUS*", KERNELS=="input*", ATTRS{name}=="Eee PC WMI hotkeys", RUN+="keymap
$name 0x6B f21"
(Continue reading)

Permalink | Reply | 1 comment |
headers
gene heskett | 2 Jan 2011 19:27
Favicon

At wits end with a Broadcom Corp BCM92046DG-CL1ROM

Greetings all;

This device, a bluetooth button/dongle, or the a7 eb101 it pairs with to 
create a virtual rs232 cable, have to be the most obstinate inanimate 
devices ever.

AIUI the BT specs, 2 devices once paired, are to remain so, even after 
powerdowns, until such time as a new pairing is performed.  Right?  Or does 
linux impose its own rules for low traffic, slow (9600 baud) bluetooth 
links?

It takes about a days messing around to finally get it to work, usually 
accomplished by unplugging it long enough for linux to detect and do the 
cleanup.  Then when plugging it back in, if one is quick enough to catch it 
before bluetoothd times out and goes away and gets blueman-manager running 
within this timeout, which appears to be in the 5 second range after its 
rediscovery, then, 1 time only per reboot of this machine, I can get it to 
work, and it works error free, with good signal strength showing in 
blueman-manager.  For possibly 12 hours or so.  At some point, blueman-
manager goes away silently, and the link is dropped and cannot be re-
established by the same procedure until I have rebooted this box again.

Pertinent (maybe) info:
current kernel: 2.6.37-rc8
current distro:	PClos, 32 bit, 100% uptodate
current hdwe:   AMD quad core phenom, 4Gb dram, 4 Tb of drives
current gui:    KDE-4.5.4

I have edited /etc/bluetooth/rfcomm.conf to:
#
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Pitt | 3 Jan 2011 09:32
Favicon
Gravatar

Re: [PATCH] Remap Eee PC touchpad toggle key to F21 used by X

Hello Chris,

chris <at> cnpbagwell.com [2011-01-01 15:44 -0600]:
> Currently, Eee PC have a hotkey that generates KEY_F13 but this
> will soon change to KEY_TOUCHPAD_TOOGLE.  Both cases do not
> work well with X.
> 
> X has defined F21 for the purpose of touchpad toggle and other
> udev keymaps align with this meaning.  Patch aligns Eee PC
> hotkey drivers with F21.

Thanks! Applied.

Martin
--

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
gene heskett | 3 Jan 2011 21:52
Favicon

At wits end with a Broadcom Corp BCM92046DG-CL1ROM

Greetings all;

Ping?  Repeat post with a few additions.

This device, a bluetooth button/dongle, or the a7 eb101 it pairs with to 
create a virtual rs232 cable, have to be the most obstinate inanimate 
devices ever.

AIUI the BT specs, 2 devices once paired, are to remain so, even after 
powerdowns, until such time as a new pairing is performed.  Right/wrong?  

It takes about a days messing around to finally get it to work, usually 
accomplished by unplugging it long enough for linux to detect and do the 
cleanup.  Then when plugging it back in, if one is quick enough to catch it 
before bluetoothd times out and goes away and gets blueman-manager running 
within this timeout, which appears to be in the 5 second range after its 
rediscovery, then, 1 time only per reboot of this machine, I can get it to 
work, and it works error free, with good signal strength showing in 
blueman-manager.  For possibly 12 hours or so.  At some point, blueman-
manager goes away silently, and the link is dropped and cannot be re-
established by the same procedure until I have rebooted both boxes again.

Pertinent (maybe) info:
current kernel: 2.6.37-rc8
current distro:	PClos, 32 bit, 100% uptodate
current hdwe:   AMD quad core phenom, 4Gb dram, 4 Tb of drives
current gui:    KDE-4.5.4

I have edited /etc/bluetooth/rfcomm.conf to:
#
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thomas Koeller | 3 Jan 2011 23:29
Picon

Failure to build ata_id

Hi,

since kernel release v2.6.35-rc1 (commit 7407e5bba2cc821950344fd1391d9ad1b7e0b397),
scsi/scsi.h is no longer part of the exported kernel headers. Since then, it has
not been possible to do a full build of udev anymore, because extras/ata_id/ata_id.c
wants to include this header.

I suppose new udev releases are tested with a current kernel? Am I missing something?

Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 1 comment |
headers
Kay Sievers | 4 Jan 2011 00:38

Re: Failure to build ata_id

On Mon, Jan 3, 2011 at 23:29, Thomas Koeller <thomas <at> koeller.dyndns.org> wrote:
> since kernel release v2.6.35-rc1 (commit 7407e5bba2cc821950344fd1391d9ad1b7e0b397),
> scsi/scsi.h is no longer part of the exported kernel headers. Since then, it has
> not been possible to do a full build of udev anymore, because extras/ata_id/ata_id.c
> wants to include this header.
>
> I suppose new udev releases are tested with a current kernel? Am I missing something?

It's not a kernel header, it's from glibc. You need a matching glibc
for these new kernel headers.

$ rpm -qf /usr/include/scsi/scsi.h
glibc-devel-2.11.3-4.1.x86_64

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Vincent Guittot | 4 Jan 2011 10:50
Favicon

[PATCH] tracing, perf : add cpu hotplug trace events

Please find below a proposal for adding new trace events for cpu
hotplug.The goal is to measure the latency of each part (kernel,
architecture and platform) and also to trace the cpu hotplug activity
with other power events. I have tested these traces events on an arm
platform

Comments are welcome.

Date: Wed, 15 Dec 2010 11:22:21 +0100
Subject: [PATCH] hotplug tracepoint

this patch adds new events for cpu hotplug tracing
* plug/unplug sequence
* architecture and machine latency measurements

Signed-off-by: Vincent Guittot <vincent.guittot <at> linaro.org>
---
include/trace/events/hotplug.h |   71 ++++++++++++++++++++++++++++++++++++++++
1 files changed, 71 insertions(+), 0 deletions(-)
create mode 100644 include/trace/events/hotplug.h

diff --git a/include/trace/events/hotplug.h b/include/trace/events/hotplug.h
new file mode 100644
index 0000000..51c86ab
--- /dev/null
+++ b/include/trace/events/hotplug.h
 <at>  <at>  -0,0 +1,71  <at>  <at> 
+#undef TRACE_SYSTEM
+#define TRACE_SYSTEM hotplug
+
(Continue reading)

Permalink | Reply | 9 comments |
headers
Guillaume Rousse | 5 Jan 2011 14:27
Picon
Gravatar

VFS issue with hardware-encrypted usb devices

(This is a repost of a message I originally sent to lkml, which seems a
better fit there).

Hello.

I'm currently playing with hardware-encrypted Imation defender USB
devices, which are USB keys/drives, using password and/or fingerprint
sensors for unlocking content:
http://www.imation.com/en-us/Imation-Products/

The main issue is that they are automatically mounted under gnome (and I
guess all other modern desktop) before being unlocked, and the VFS
doesn't likes the behind-the-scene changes very much.

Here the syslog trace when plugging (the normal partition is seen as a
CD-ROM, the encrypted one as a standard removal drive):
Jan  3 15:14:07 beria kernel: : usb 2-1: new high speed USB device using
ehci_hcd and address 8
Jan  3 15:14:08 beria kernel: : usb 2-1: New USB device found,
idVendor=0718, idProduct=0682
Jan  3 15:14:08 beria kernel: : usb 2-1: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
Jan  3 15:14:08 beria kernel: : usb 2-1: Product: Defender F200
Jan  3 15:14:08 beria kernel: : usb 2-1: Manufacturer: Imation
Jan  3 15:14:08 beria kernel: : usb 2-1: SerialNumber: F5121031F003008E
Jan  3 15:14:08 beria kernel: : scsi10 : usb-storage 2-1:1.0
Jan  3 15:14:09 beria kernel: : scsi 10:0:0:0: CD-ROM
Defender F200 Application 0001 PQ: 0 ANSI: 2
Jan  3 15:14:09 beria kernel: : sr0: scsi-1 drive
Jan  3 15:14:09 beria kernel: : sr 10:0:0:0: Attached scsi generic sg1
(Continue reading)

Permalink | Reply | 0 comments |
headers
KESHAV P.R. | 5 Jan 2011 20:13
Picon

Udev GPT GUID support

Hi all,
         I am not a programmer, just a user. I use Archlinux x86_64
and I was thinking about using Unique GUID of a GPT partition to
identify root partition from the bootloader's (syslinux and grub2 in
my case) kernel parameter line. Right now I use
root=/dev/disk/by-uuid/xxxxxxxxxxxxx (FS-UUID) and want to try
PART-UUID. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b5af921ec02333e943efb59aca4f56b78fc0e100
does not work in my case (x86_64 kernel 2.6.37-rc8). How about
creating /dev/disk/by-part-uuid/xxxxxxx symlinks and renaming the
previous dir to /dev/disk/by-fs-uuid/xxxxxxxxxx (for clarity). The
Unique GUID can be obtained using GPT fdisk
http://rodsbooks.com/gdisk/ (I do not know whether util-linux-ng can
be used here). Thanks in advance.

Regards.

Keshav
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Matt Domsch | 5 Jan 2011 23:44
Picon
Favicon

Re: [PATCH] Export ACPI _DSM provided firmware instance number and string name to sysfs

On Thu, Dec 23, 2010 at 11:24:36AM -0800, Narendra_K <at> Dell.com wrote:
> Please find the version 2 of the patch.
> 
> V1 -> V2:
> 
> The attribute 'index' is changed to 'acpi_index' as the semantics of
> SMBIOS provided device type instance and ACPI _DSM provided instance
> number are different.
> 
> From: Narendra K <narendra_k <at> dell.com>
> Subject: [PATCH V2] Export ACPI _DSM provided firmware instance number and string to sysfs
> 
> This patch exports ACPI _DSM (Device Specific Method) provided firmware
> instance number and string name of PCI devices as defined by
> 'PCI Firmware Specification Revision 3.1' section 4.6.7.( DSM for Naming
> a PCI or PCI Express Device Under Operating Systems) to sysfs.

Thanks Narendra and Jordan.

Jesse, how does this look for -next please?

Thanks,
Matt

--

-- 
Matt Domsch
Technology Strategist
Dell | Office of the CTO
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
(Continue reading)

Permalink | Reply | 1 comment |

Gmane