Hi,
Here is my new set of input patches, most important IMHO is serio sysfs
integration. It is not complete in sense that we need add attributes to
individual drivers (like rate and resolution and protocol to psmouse)
and create some platform devices for i8042, q40kbd, etc so serio ports
would have parents. But the core integration is done. Unfortunately I do
not have 90% hardware to test my changes so there could be some problems,
although I tried to compile everything I could.
The patches are against Vojtech's tree and should apply to -mm as well.
01-psmouse-kvm-sync.patch
- when getting partial packet (usually KVM resets mouse from IMPS/2
to bare PS/2 count it in out_of_sync counter so psmouse.resetafter
logic has a chance to reconnect and reestablish proper protocol;
set default value for psmouse.resetafter to 20 (was 0, disabled)
02-psmouse-state-locking.patch
- Acquire underlying serio lock when changing psmouse state to
prevent interrupt handler runniong on us
03-serio-connect-mandatory.patch
- Make serio driviers connect/disconnect methods mandatory as these
methods open/close serio ports and link ports and drivers together
04-serio-rename-1.patch
- Rename serio->driver to serio->port_data as with sysfs integration
driver is not the best name for arbitrary data
05-serio-rename-2.patch
- Rename serio_dev to serio_driver as they are drivers in sysfs sense
06-serio-dynamic-alloc.patch
- Switch from static to dynamic serio port allocation so serio ports
drivers can be freely unloaded even if not all references to ports
are dropped (sysfs req.)
07-serio-no-recursion.patch
- do not do recursive discovery of children ports, needed for sysfs
and generally better for stack
08-serio-sysfs.patch
- sysfs integration. register ports and drivers in driver model, link
them all together.
09-serio-rebind.patch
- allow user to disconnect or rebind serio port by writing appropriate
data to it's sysfs attribute:
echo -n "psmouse" > /sys/bus/serio/devices/serio0/driver
echo -n "none" > /sys/bus/serio/devices/serio0/driver
10-serio-manual-bind.patch
- allow marking some drivers as requiring manual bind (to be used when
driver does not do automatic HW discovery)
11-serio_raw.patch
- raw access to serio data ala 2.4 /dev/psaux
Vojtech, if you like some patches and want to pull any of it drop me a
note and I'll push it on bkbits.
--
Dmitry
On Fri, 2004-06-18 03:44:46 -0500, Dmitry Torokhov <[email protected]>
wrote in message <[email protected]>:
> would have parents. But the core integration is done. Unfortunately I do
> not have 90% hardware to test my changes so there could be some problems,
> although I tried to compile everything I could.
Maybe I'll test at least my two babies (vsxxxaa and lkkbd) to work with
these patches. They're using normal serial ports (ISA + USB) with
inputattach, these should already have parents, right?
MfG, JBG
--
Jan-Benedict Glaw [email protected] . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier B?rger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
On Friday 18 June 2004 04:21 am, Jan-Benedict Glaw wrote:
> On Fri, 2004-06-18 03:44:46 -0500, Dmitry Torokhov <[email protected]>
> wrote in message <[email protected]>:
>
> > would have parents. But the core integration is done. Unfortunately I do
> > not have 90% hardware to test my changes so there could be some problems,
> > although I tried to compile everything I could.
>
> Maybe I'll test at least my two babies (vsxxxaa and lkkbd) to work with
> these patches. They're using normal serial ports (ISA + USB) with
> inputattach, these should already have parents, right?
>
Right now nothing has a parent except for passthrough ports. I will do more
patches later, but when I as looking at the serial port code it seemed that
ther actual devices (as in struct device) were not available for ttys yet.
Please corect me if I am mistaken.
--
Dmitry
On Fri, 2004-06-18 03:44:46 -0500, Dmitry Torokhov <[email protected]>
wrote in message <[email protected]>:
> The patches are against Vojtech's tree and should apply to -mm as well.
However, they won't apply onto Linus' tree and cause rejects in a good
number of "interesting" files.
MfG, JBG
--
Jan-Benedict Glaw [email protected] . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier B?rger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
> > The patches are against Vojtech's tree and should apply to -mm as well.
>
> However, they won't apply onto Linus' tree and cause rejects in a good
> number of "interesting" files.
Well, I do not consider it tested enough to be ready for Linus yet :)
I am thinking about publushing my input-sysfs bk tree... Will there
be an interest in it or you just want a patch against the vanilla 2.6.7?
I can do a wholesale patch but splitting my changes from other stuff in
Vojtech's tree does not sound very appealing...
--
Dmitry
On Fri, 2004-06-18 13:33:40 -0700, Dmitry Torokhov <[email protected]>
wrote in message <[email protected]>:
> > > The patches are against Vojtech's tree and should apply to -mm as well.
> > However, they won't apply onto Linus' tree and cause rejects in a good
> > number of "interesting" files.
>
> I am thinking about publushing my input-sysfs bk tree... Will there
> be an interest in it or you just want a patch against the vanilla 2.6.7?
I'd (personally) prefer a patch to Linus' tree, but really a patch. I
don't use bk (various reasons, don't flame, asbestos already prepared).
MfG, JBG
--
Jan-Benedict Glaw [email protected] . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier B?rger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
On Fri, 2004-06-18 13:33:40 -0700, Dmitry Torokhov <[email protected]>
wrote in message <[email protected]>:
> > However, they won't apply onto Linus' tree and cause rejects in a good
> > number of "interesting" files.
>
> Well, I do not consider it tested enough to be ready for Linus yet :)
> I am thinking about publushing my input-sysfs bk tree... Will there
> be an interest in it or you just want a patch against the vanilla 2.6.7?
> I can do a wholesale patch but splitting my changes from other stuff in
> Vojtech's tree does not sound very appealing...
As I said, I'd love to see a -linus based patch, simply because I
basically work with exactly this as my base. However, I can also try to
get another base to start from.
MfG, JBG
--
Jan-Benedict Glaw [email protected] . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier B?rger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
On Saturday 19 June 2004 03:05 pm, Jan-Benedict Glaw wrote:
> On Fri, 2004-06-18 13:33:40 -0700, Dmitry Torokhov <[email protected]>
> wrote in message <[email protected]>:
> > > However, they won't apply onto Linus' tree and cause rejects in a good
> > > number of "interesting" files.
> >
> > Well, I do not consider it tested enough to be ready for Linus yet :)
> > I am thinking about publushing my input-sysfs bk tree... Will there
> > be an interest in it or you just want a patch against the vanilla 2.6.7?
> > I can do a wholesale patch but splitting my changes from other stuff in
> > Vojtech's tree does not sound very appealing...
>
> As I said, I'd love to see a -linus based patch, simply because I
> basically work with exactly this as my base. However, I can also try to
> get another base to start from.
>
Ok, how about this:
http://www.geocities.com/dt_or/input/2_6_7/
00-bk-input.patch.gz and 00-bk-sysfs.patch.gz are pulls from Vojtech's and
Greg's threes diffed against 2.6.7 - that's what I use as a baseline.
The rest of the patches are the ones that I posted earlier.
--
Dmitry