From: Marcin Tolysz <tolysz@gmail.com>
To: linux-input@vger.kernel.org
Subject: [RFC] Simple but effective way of changing HID device descriptors (resent)
Date: Thu, 24 Dec 2009 02:29:47 +0000 [thread overview]
Message-ID: <4B32D21B.9090800@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2559 bytes --]
Simple but effective way of changing HID device descriptors using
firmware loading mechanism.
Just place your new descriptor in a location specified by driver
i.e. somewhere in /lib/firmware/hid/
If it is there it will replace HID descriptor from the device.
I do not do any parsing or checking, as it is done by hid driver.
Signed-off-by: Marcin Tolysz <tolysz@gmail.com>
---
drivers/hid/hid-core.c | 26 +++++++++++++++++++++++++-
1 files changed, 25 insertions(+), 1 deletions(-)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 80792d3..5d8d656 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -27,6 +27,7 @@
#include <linux/wait.h>
#include <linux/vmalloc.h>
#include <linux/sched.h>
+#include <linux/firmware.h>
#include <linux/hid.h>
#include <linux/hiddev.h>
@@ -640,6 +641,10 @@ int hid_parse_report(struct hid_device *device,
__u8 *start,
struct hid_item item;
__u8 *end;
int ret;
+ const struct firmware *fw;
+ int succ;
+ char *file;
+
static int (*dispatch_type[])(struct hid_parser *parser,
struct hid_item *item) = {
hid_parser_main,
@@ -650,10 +655,27 @@ int hid_parse_report(struct hid_device *device,
__u8 *start,
if (device->driver->report_fixup)
device->driver->report_fixup(device, start, size);
+ /* Now load a hid descriptor from a file firmware
+ ignoring this fixup thing */
+ file=kmalloc(29, GFP_KERNEL);
+
sprintf(file,"hid/%04X:%04X:%04X:%04X.bin",device->bus,device->vendor,device->product,device->version);
+
+ succ = request_firmware(&fw, file, &device->dev);
+
+ if (succ)
+ printk(KERN_INFO "To relace HID descriptor place it in
/lib/firmaware/%s\n", file);
+ else{
+ start = fw->data;
+ size = fw->size;
+ printk(KERN_INFO "HID descriptor relaced with /lib/firmaware/%s\n",
file);
+ }
+ kfree(file);
device->rdesc = kmalloc(size, GFP_KERNEL);
- if (device->rdesc == NULL)
+ if (device->rdesc == NULL){
+ if(!succ)release_firmware(fw);
return -ENOMEM;
+ }
memcpy(device->rdesc, start, size);
device->rsize = size;
@@ -690,6 +712,7 @@ int hid_parse_report(struct hid_device *device, __u8
*start,
dbg_hid("unbalanced delimiter at end of report description\n");
goto err;
}
+ if(!succ)release_firmware(fw);
vfree(parser);
return 0;
}
@@ -697,6 +720,7 @@ int hid_parse_report(struct hid_device *device, __u8
*start,
dbg_hid("item fetching failed at offset %d\n", (int)(end - start));
err:
+ if(!succ)release_firmware(fw);
vfree(parser);
return ret;
}
-- 1.6.5.7
[-- Attachment #2: 0001-Simple-but-effective-way-of-chaging-HID-device-descr.patch --]
[-- Type: text/x-patch, Size: 2784 bytes --]
>From 85bc06073ad4d18f44757c2c72f9f8409ecf3ac5 Mon Sep 17 00:00:00 2001
From: Marcin Tolysz <tolysz@gmail.com>
To: <linux-input@vger.kernel.org>
Date: Thu, 24 Dec 2009 01:40:34 +0000
Subject: [RFC] Simple but effective way of chaging HID device descriptors
Simple but effective way of chaging HID device descriptorsusing firmware loading mechanism.
Just place your new descriptor in a location specified by driver
i.e. somewhere in /lib/firmware/hid/
If it is there it will replace HID descriptor from the device.
I do not do any parsing or checking, as it is done by hid driver.
Signed-off-by: Marcin Tolysz <tolysz@gmail.com>
---
drivers/hid/hid-core.c | 26 +++++++++++++++++++++++++-
1 files changed, 25 insertions(+), 1 deletions(-)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 80792d3..5d8d656 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -27,6 +27,7 @@
#include <linux/wait.h>
#include <linux/vmalloc.h>
#include <linux/sched.h>
+#include <linux/firmware.h>
#include <linux/hid.h>
#include <linux/hiddev.h>
@@ -640,6 +641,10 @@ int hid_parse_report(struct hid_device *device, __u8 *start,
struct hid_item item;
__u8 *end;
int ret;
+ const struct firmware *fw;
+ int succ;
+ char *file;
+
static int (*dispatch_type[])(struct hid_parser *parser,
struct hid_item *item) = {
hid_parser_main,
@@ -650,10 +655,27 @@ int hid_parse_report(struct hid_device *device, __u8 *start,
if (device->driver->report_fixup)
device->driver->report_fixup(device, start, size);
+ /* Now load a hid descriptor from a file firmware
+ ignoring this fixup thing */
+ file=kmalloc(29, GFP_KERNEL);
+ sprintf(file,"hid/%04X:%04X:%04X:%04X.bin",device->bus,device->vendor,device->product,device->version);
+
+ succ = request_firmware(&fw, file, &device->dev);
+
+ if (succ)
+ printk(KERN_INFO "To relace HID descriptor place it in /lib/firmaware/%s\n", file);
+ else{
+ start = fw->data;
+ size = fw->size;
+ printk(KERN_INFO "HID descriptor relaced with /lib/firmaware/%s\n", file);
+ }
+ kfree(file);
device->rdesc = kmalloc(size, GFP_KERNEL);
- if (device->rdesc == NULL)
+ if (device->rdesc == NULL){
+ if(!succ)release_firmware(fw);
return -ENOMEM;
+ }
memcpy(device->rdesc, start, size);
device->rsize = size;
@@ -690,6 +712,7 @@ int hid_parse_report(struct hid_device *device, __u8 *start,
dbg_hid("unbalanced delimiter at end of report description\n");
goto err;
}
+ if(!succ)release_firmware(fw);
vfree(parser);
return 0;
}
@@ -697,6 +720,7 @@ int hid_parse_report(struct hid_device *device, __u8 *start,
dbg_hid("item fetching failed at offset %d\n", (int)(end - start));
err:
+ if(!succ)release_firmware(fw);
vfree(parser);
return ret;
}
--
1.6.5.7
next reply other threads:[~2009-12-24 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 2:29 Marcin Tolysz [this message]
2009-12-24 8:39 ` [RFC] Simple but effective way of changing HID device descriptors (resent) Antonio Ospite
2009-12-31 17:28 ` Marcin Tolysz
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=4B32D21B.9090800@gmail.com \
--to=tolysz@gmail.com \
--cc=linux-input@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).