)
It also can apply on 2.6.17.6 and 2.6.17.8 at least.
PS: I have not Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/usbnek4k.c
linux-2.6.17.7/drivers/usb/input/usbn
Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/btp2118.c
linux-2.6.17.7/drivers/usb/input/btp2118.c
--- linux-2.6.17.7/drivers/usb/input.orig/btp2118.c 1970-01-01
For simple, I merge the changes with two drivers. you can use two drivers as
example.
It also can apply on 2.6.17.6 and 2.6.17.8 at least.
PS: I have not Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp
bugfixes.
It also can apply on 2.6.17.6 and 2.6.17.8 at least.
PS: I have not Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/hid-core.c
linux-2.6.17.7/drivers/usb/inp
. some bugfixes.
It also can apply on 2.6.17.6 and 2.6.17.8 at least.
PS: I have not Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/hid-core.c
linux-2.6.17.7/drivers/usb
For simple, I merge the changes with two drivers. you can use two drivers as
example.
It also can apply on 2.6.17.6 and 2.6.17.8 at least.
PS: I have not Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp
Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/btp2118.c
linux-2.6.17.7/drivers/usb/input/btp2118.c
--- linux-2.6.17.7/drivers/usb/input.orig/btp2118.c 1970-01-01
)
It also can apply on 2.6.17.6 and 2.6.17.8 at least.
PS: I have not Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/usbnek4k.c
linux-2.6.17.7/drivers/usb/input/usbn
policy analysis reported: Your address is not liked source
for email
Is it looked my mail as spam mail? Who should I send to for help me
resolving this problem?
Alexey Dobriyan wrote:
> On Wed, Aug 16, 2006 at 10:09:07AM +0800, liyu wrote:
>
>> --- linux-2.6.17.7/drivers/usb/inp
Alexey Dobriyan wrote:
> On Wed, Aug 16, 2006 at 10:09:12AM +0800, liyu wrote:
>
>> --- linux-2.6.17.7/drivers/usb/input.orig/btp2118.c
>> +++ linux-2.6.17.7/drivers/usb/input/btp2118.c
>> +static struct usage_block btp_ff_usage_block[] = {
>> +USAGE_BLOCK(USAG
For simple, I merge the changes with two drivers. you can use two drivers as
example.
It also can apply on 2.6.17.6 and 2.6.17.8 at least.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/Kconfig
linux-2.6.17.7/drivers/usb/input/Kconfig
---
also can apply on 2.6.17.6 and 2.6.17.8 at least.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/hid-core.c
linux-2.6.17.7/drivers/usb/input/hid-core.c
--- linux-2.6.17.7/drivers/usb/input.orig/hid-core.c2006-07-25
11:36:01.
can apply on 2.6.17.6 and 2.6.17.8 at least.
PS: I have not Subscribe linux-usb-devel maillist, please CC me your reply,
thanks.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.17.7/drivers/usb/input.orig/btp2118.c
linux-2.6.17.7/drivers/usb/input/btp2118.c
---
--- linux-2.6.17.7/Documentation/input/simple-hid.txt.noexist
1970-01-01 08:00:00.0 +0800
+++ linux-2.6.17.7/Documentation/input/simple-hid.txt2006-08-17
20:24:36.0 +0800
@@ -0,0 +1,236 @@
+==
+HID device simple driver interface
+==
change. Of course, you
should use patch with -p1 option, not -p0.
Signed-off-by: Liyu <[EMAIL PROTECTED]>
diff -Naurp linux-2.6.18-rc4/drivers/usb/input.orig/hid-core.c
linux-2.6.18-rc4/drivers/usb/input/hid-core.c
--- linux-2.6.18-rc4/drivers/usb/input.orig/hid-core.c 2006-08-19
Robert Marquardt wrote:
> Li Yu wrote:
>> +#define USAGE_ZOOM_IN0x22d
>
> I have a 100K file of probably all HID usages available.
> It started its life as a conversion to Pascal of hidusage.h but is now
> 10 times bigger than that file. I can easily convert this back to C.
> Is there any inter
I think the source file should be the original data source (MS file),
The Pascal file is one derivation of from, it still may be under the MS
license.
That is my guess, I am not familiar with the legal very well.
Robert Marquardt wrote:
> Liyu wrote:
>
>> It is great resource, and
Dmitry Torokhov wrote:
> If we define HID "bus" allowing drivers to bind on VID:PID and provide
> default library module for parsing HID reports and providing access to
> HID transports (USB/BT) then writing tiny drivers adjusting just a
> part of hid_input_event and relying on default implemenatta
hcd and address 3
Goodluck.
-Liyu
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief su
hcd and address 3
Goodluck.
-Liyu
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief su
-core/dvbdev.h and
> drivers/media/dvb/dvb-core/dvb_frontend.c.
>
>
This means also can load module dynamically. In apparently, I think it
have two weaknesses:
1. It require module have one exported symbol at least.
2. We must handle life cycle of module by myself.
Is
, except when it failed to init itself.
Are these purposely?
-Liyu
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT
, except when it failed to init itself.
Are these purposely?
-Liyu
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opin
Liyu wrote:
> Hi.
>
> In hid-input, It seem we only call input_allocate_device(), but not
> call input_free_device() at anywhere. Is there a memory leak here? Even,
> I can not found this invoke in drivers/usb/hid*.c.
>
>
I see. it is freed by input_class.release()
Signed-off-by: Liyu <[EMAIL PROTECTED]>
--- linux-2.6.18/Documentation/input/no-such.txt 1970-01-01
08:00:00.0 +0800
+++ linux-2.6.18/Documentation/input/simple-hid.txt 2006-10-12
09:34:42.0 +0800
@@ -0,0 +1,251 @@
+==
+HID device simple
Jiri Kosina wrote:
> Do you think that you could wait a little bit more, after the split has
> been done? (it's currently planned approximately after 2.6.20-rc1). It
> seems to me that your patches will apply almost cleanly on top of the
> split patches (you will have to change the pathnames, of
26 matches
Mail list logo
