linuxconsole-dev

Synced to 2.4.12

[James S. <jsi...@tr...>]

I completed the syncing to 2.4.12 and tested it out on my local machine.
It works fine.

Please NOTE!!!! You must do a make mrproper when sync up our tree or use
a free tree with ruby ontop. Otherwise you will have problems. I did. This
week I'm going to start working on ruby at work in the next few days so
much more coding will be done :-) 


P.S
   Anyone try ruby on a IBM thinkpad? I did and the touch pad (PS/2 mouse)
didn't work. Also I had the same problem on a Compaq Laptop. 

Re: Synced to 2.4.12

[Johann D. <jo...@Do...>]

On Sun, 14 Oct 2001, James Simmons wrote:

> 
> I completed the syncing to 2.4.12 and tested it out on my local machine.
> It works fine.
> 
> Please NOTE!!!! You must do a make mrproper when sync up our tree or use
> a free tree with ruby ontop. Otherwise you will have problems. I did. This
> week I'm going to start working on ruby at work in the next few days so
> much more coding will be done :-) 
> 

Good news, it almost worked on my PC. But without smp :(
By almost, I mean that the kernel booted, and X started. Unfortunately, my
PS2 keyboard refused to work.

-- 
Johann Deneux

Re: Synced to 2.4.12

[James S. <jsi...@tr...>]

> Good news, it almost worked on my PC. But without smp :(

Ah. So it is a race condition on SMP. I don't have a SMP box so I haven't
seen this problem. Do you see anything? 

> By almost, I mean that the kernel booted, and X started. Unfortunately, my
> PS2 keyboard refused to work.

Hm. Strange. It should of put the "keyboard" in raw mode. The codes sent
then are the one in drivers/char/keyboard.c. I will have to test it with X
windows.

Re: Synced to 2.4.12

[Johann D. <jo...@Do...>]

On Wed, 17 Oct 2001, James Simmons wrote:

> 
> > Good news, it almost worked on my PC. But without smp :(
> 
> Ah. So it is a race condition on SMP. I don't have a SMP box so I haven't
> seen this problem. Do you see anything? 

No, I don't. The problem is that the source would not compile. Still the
same problem with global_irq_lock in bust_spinlocks.
What is global_irq_lock suppose to do, by the way ? To disable irqs on all
cpus ?

> 
> > By almost, I mean that the kernel booted, and X started. Unfortunately, my
> > PS2 keyboard refused to work.
> 
> Hm. Strange. It should of put the "keyboard" in raw mode. The codes sent
> then are the one in drivers/char/keyboard.c. I will have to test it with X
> windows.

It did not work for the console either. But that may just be me who
misconfigured the kernel. I read input.txt several times, but it seems to
focus on USB keyboards and mice. I therefore have some difficulties to
apply it to my "simple" PS2 keyboard. I understand there are a few changes
to do to have the mouse working (patch gpm, change XF86Config). Is there
anything similar to do with the keyboard ?

-- 
Johann Deneux

Re: Synced to 2.4.12

[James S. <jsi...@tr...>]

> > Ah. So it is a race condition on SMP. I don't have a SMP box so I haven't
> > seen this problem. Do you see anything? 
> 
> No, I don't. The problem is that the source would not compile. Still the
> same problem with global_irq_lock in bust_spinlocks.
> What is global_irq_lock suppose to do, by the way ? To disable irqs on all
> cpus ?

Ah!! Yes it is to disable irqs. I will have to disable it. I really wish
global_irq_lock was universal on all platforms. Its not :-(  I will commit
it out.

> It did not work for the console either. But that may just be me who
> misconfigured the kernel. I read input.txt several times, but it seems to
> focus on USB keyboards and mice. 

True. It is USB centeric but the PS/2 keybaord should still behave as a
USB keyboard. 

> I therefore have some difficulties to
> apply it to my "simple" PS2 keyboard. I understand there are a few changes
> to do to have the mouse working (patch gpm, change XF86Config). Is there
> anything similar to do with the keyboard ?

It should behave the same as a USB keyboard. Since X uses the console in
raw mode for keyboard input it should behave the same. You don't need to
do anything special. What is your configuration?
 
 

Re: Synced to 2.4.12

[Johann D. <jo...@Do...>]

On Thu, 18 Oct 2001, James Simmons wrote:

> 
> > > Ah. So it is a race condition on SMP. I don't have a SMP box so I haven't
> > > seen this problem. Do you see anything? 
> > 
> > No, I don't. The problem is that the source would not compile. Still the
> > same problem with global_irq_lock in bust_spinlocks.
> > What is global_irq_lock suppose to do, by the way ? To disable irqs on all
> > cpus ?
> 
> Ah!! Yes it is to disable irqs. I will have to disable it. I really wish
> global_irq_lock was universal on all platforms. Its not :-(  I will commit
> it out.

But isn't it needed ?

> > It did not work for the console either. But that may just be me who
> > misconfigured the kernel. I read input.txt several times, but it seems to
> > focus on USB keyboards and mice. 
> 
> True. It is USB centeric but the PS/2 keybaord should still behave as a
> USB keyboard. 
> 
> > I therefore have some difficulties to
> > apply it to my "simple" PS2 keyboard. I understand there are a few changes
> > to do to have the mouse working (patch gpm, change XF86Config). Is there
> > anything similar to do with the keyboard ?
> 
> It should behave the same as a USB keyboard. Since X uses the console in
> raw mode for keyboard input it should behave the same. You don't need to
> do anything special. What is your configuration?
>

Attached is the .config I used. If you meant to ask about my hardware, I
am afraid I have no idea what kind of PS2 keyboard it is. I did not even
know there were several kinds. I tried to enable "XT keyboard" and "AT and
PS/2 keyboards" separately and then together in section "PS/2 port input
devices". No success so far.

-- 
Johann Deneux

Re: Synced to 2.4.12

[James S. <jsi...@tr...>]

> > Ah!! Yes it is to disable irqs. I will have to disable it. I really wish
> > global_irq_lock was universal on all platforms. Its not :-(  I will commit
> > it out.
> 
> But isn't it needed ?

Hm. The problem is some serial drivers do a __global_irq_lock. It is only
a issue when the kernel oops.

> Attached is the .config I used. 

I see the problem. You have to select one of the controllers. For the PC
it should be "i8042 aux+kbd controller". The i8042 chipset is used on alot
of platforms. Each platform is a little different so we have hooks from
serio to help handle these differences.  

Re: Synced to 2.4.12

[Johann D. <jo...@Do...>]

On Thu, 18 Oct 2001, James Simmons wrote:

> 
> > Attached is the .config I used. 
> 
> I see the problem. You have to select one of the controllers. For the PC
> it should be "i8042 aux+kbd controller". The i8042 chipset is used on alot
> of platforms. Each platform is a little different so we have hooks from
> serio to help handle these differences.  
> 
It indeedd works better. Howeverr, it is still not perrfect. As yoou may
notice, the key-repeat behaves quite oddly. It is disabledd when I try to
use it, but some characters are sometimes reepeated more than the
intenddeed  amount (I am using the linuxconsole tree right now). But at
least I am making some progress  ;)

-- 
Johann Deneux

Re: Synced to 2.4.12

[James S. <jsi...@tr...>]

> It indeedd works better. Howeverr, it is still not perrfect. As yoou may
> notice, the key-repeat behaves quite oddly. It is disabledd when I try to
> use it, but some characters are sometimes reepeated more than the
> intenddeed  amount (I am using the linuxconsole tree right now). But at
> least I am making some progress  ;)

I haven't figured it out yet. kbd_rate sets the type rate but it uses
ioperm to change those values. It directly playes with the hardware. So I
moved it out of the way to prevent that. Something else is accessing the
ioctl call for the console system to change the the keyboard rates. I did
change the code for that ioctl to use the input api. Unfortunely theri is
a annoying bug in the code. That has to be worked out anyways since you
have for the console system do things you can set the repeat rate for. The
beep noise and the keyboard. I think it is getting confussed between the
two. Okay off to finish my white paper on the console project. Yes I'm
writing a white paper to explain everything that has been done so far.