Re: About atags_proc buffer size

2013-09-27 Thread Vojtech Bocek
wrote: > On Fri, Sep 27, 2013 at 11:09:13PM +0200, Vojtech Bocek wrote: >> It only needs to survive until init_atags_procfs is called, because it is >> copied to another buffer for procfs entry. Can I be sure it survives until >> that? My guess is that it is likely to sur

Re: About atags_proc buffer size

2013-09-27 Thread Vojtech Bocek
) and I unfortunately can't remember the first one - I discarded it as usual Android kernel's mess. On 27.9.2013 22:47, Russell King - ARM Linux wrote: > On Fri, Sep 27, 2013 at 10:25:45PM +0200, Vojtech Bocek wrote: >> I want to ask something about atags_proc.c implementation.

About atags_proc buffer size

2013-09-27 Thread Vojtech Bocek
of such modification[1]. If this is okay, I can create a proper patch and submit it. Yours, Vojtech Bocek [1]: https://github.com/Tasssadar/kexec-tools/commit/c6844e1ddb13a6b60cfefcb01c3843da97d6174c --- diff --git a/arch/arm/kernel/atags_proc.c b/arch/arm/kernel/atags_proc.c index c7ff807..12cc483 100644

About atags_proc buffer size

2013-09-27 Thread Vojtech Bocek
of such modification[1]. If this is okay, I can create a proper patch and submit it. Yours, Vojtech Bocek [1]: https://github.com/Tasssadar/kexec-tools/commit/c6844e1ddb13a6b60cfefcb01c3843da97d6174c --- diff --git a/arch/arm/kernel/atags_proc.c b/arch/arm/kernel/atags_proc.c index c7ff807..12cc483 100644

Re: About atags_proc buffer size

2013-09-27 Thread Vojtech Bocek
) and I unfortunately can't remember the first one - I discarded it as usual Android kernel's mess. On 27.9.2013 22:47, Russell King - ARM Linux wrote: On Fri, Sep 27, 2013 at 10:25:45PM +0200, Vojtech Bocek wrote: I want to ask something about atags_proc.c implementation. Currently, it uses

Re: About atags_proc buffer size

2013-09-27 Thread Vojtech Bocek
wrote: On Fri, Sep 27, 2013 at 11:09:13PM +0200, Vojtech Bocek wrote: It only needs to survive until init_atags_procfs is called, because it is copied to another buffer for procfs entry. Can I be sure it survives until that? My guess is that it is likely to survive, but not certain. I

Re: [PATCH 1/1] Input: joydev - fix axes values sent in initial js_event

2012-11-01 Thread Vojtech Bocek
. = >From be5bbc627e5c8ccfea240deef6a68b10f7f1ff40 Mon Sep 17 00:00:00 2001 From: Vojtech Bocek Date: Thu, 1 Nov 2012 17:34:34 +0100 Subject: [PATCH 1/1] Input: joydev - fix axes values sent in initial js_event Initial input ABS events can't reach joydev because it is not opened

Re: [PATCH 1/1] Input: joydev - fix axes values sent in initial js_event

2012-11-01 Thread Vojtech Bocek
. = From be5bbc627e5c8ccfea240deef6a68b10f7f1ff40 Mon Sep 17 00:00:00 2001 From: Vojtech Bocek vbo...@gmail.com Date: Thu, 1 Nov 2012 17:34:34 +0100 Subject: [PATCH 1/1] Input: joydev - fix axes values sent in initial js_event Initial input ABS events can't reach joydev because

Re: [PATCH 1/1] Input: joydev - fix axes values sent in initial js_event

2012-09-13 Thread Vojtech Bocek
2012/9/13, Dmitry Torokhov : > On Wed, Sep 05, 2012 at 10:09:57PM +0200, Vojtěch Boček wrote: > > This makes sense. Just to confirm - have you tried the patch and > verified it works for you? > > Thanks. > > -- > Dmitry > Yes, I did. Only one thing is incorrect(?). When I plug the joystick in,

Re: [PATCH 1/1] Input: joydev - fix axes values sent in initial js_event

2012-09-13 Thread Vojtech Bocek
2012/9/13, Dmitry Torokhov dmitry.torok...@gmail.com: On Wed, Sep 05, 2012 at 10:09:57PM +0200, Vojtěch Boček wrote: This makes sense. Just to confirm - have you tried the patch and verified it works for you? Thanks. -- Dmitry Yes, I did. Only one thing is incorrect(?). When I plug the

[PATCH 1/1] Input: joydev - fix axes values sent in initial js_event

2012-08-13 Thread Vojtech Bocek
Initial input event has not yet arrived in joydev_connect() where values are set, which means default values of input_absinfo are used for init event, not the actual values from joystick. Signed-off-by: Vojtech Bocek --- drivers/input/joydev.c |9 +++-- 1 file changed, 7 insertions

[PATCH 1/1] Input: joydev - fix axes values sent in initial js_event

2012-08-13 Thread Vojtech Bocek
Initial input event has not yet arrived in joydev_connect() where values are set, which means default values of input_absinfo are used for init event, not the actual values from joystick. Signed-off-by: Vojtech Bocek vbo...@gmail.com --- drivers/input/joydev.c |9 +++-- 1 file changed, 7