linuxconsole-dev

HID stuff broken.

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

I just synced up to 2.5.1 and the USB layer has changed a lot. So the HID
stuff doesn't work at present. Could you fix it? 


   . ---
   |o_o |
   |:_/ |   Give Micro$oft the Bird!!!!
  //   \ \  Use Linux!!!!
 (|     | )
 /'_   _/`\
 ___)=(___/

Re: HID stuff broken.

[Vojtech P. <vo...@su...>]

On Wed, Dec 26, 2001 at 01:11:27PM -0800, James Simmons wrote:

> I just synced up to 2.5.1 and the USB layer has changed a lot.

Wonderful!

> So the HID stuff doesn't work at present. Could you fix it? 

Yes, of course. I'll try to do that today.

-- 
Vojtech Pavlik
SuSE Labs

Re: HID stuff broken.

[Vojtech P. <vo...@su...>]

On Thu, Dec 27, 2001 at 10:46:32AM +0100, Vojtech Pavlik wrote:

> On Wed, Dec 26, 2001 at 01:11:27PM -0800, James Simmons wrote:
> 
> > I just synced up to 2.5.1 and the USB layer has changed a lot.
> 
> Wonderful!
> 
> > So the HID stuff doesn't work at present. Could you fix it? 
> 
> Yes, of course. I'll try to do that today.

Done. The Input stuff (and namely HID/HIDBP) now compiles fine again on
2.5.1. I tried to boot that kernel, and failed with 'unable to open the
initial console' message from I think the init process. I do have only
VGA console enabled (no fbcon ...).

-- 
Vojtech Pavlik
SuSE Labs

Re: HID stuff broken.

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

> Done. The Input stuff (and namely HID/HIDBP) now compiles fine again on
> 2.5.1. I tried to boot that kernel, and failed with 'unable to open the
> initial console' message from I think the init process. I do have only
> VGA console enabled (no fbcon ...).

You must have more than one keybaord attached but only one display. I ran
into this problem to. I will fix it today. The problem is the way a struct
vt_struct is added to the link list versus how a keybaord is attached.
When a new vt_struct is added to the link list it is placed int front of
the link list. This means the last VT in the list is the first VT. Now
when a keyboard is detected it scans the VT list from the head to the end. 
That is why the no console error. I will work on the problem right now.

Re: HID stuff broken.

[Vojtech P. <vo...@su...>]

On Thu, Dec 27, 2001 at 09:31:39AM -0800, James Simmons wrote:
> 
> > Done. The Input stuff (and namely HID/HIDBP) now compiles fine again on
> > 2.5.1. I tried to boot that kernel, and failed with 'unable to open the
> > initial console' message from I think the init process. I do have only
> > VGA console enabled (no fbcon ...).
> 
> You must have more than one keybaord attached but only one display.

Umm, I think I have just one keyboard. But at the time of the error
message the keyboard probably wasn't connected, being USB and with my
bad USB active extension cable, which needs to be unplugged and
replugged after each boot to detect the devices on it.

So it's one-display-no-keyboard case. It works fine with 2.4.14-ruby.

> I ran
> into this problem to. I will fix it today. The problem is the way a struct
> vt_struct is added to the link list versus how a keybaord is attached.
> When a new vt_struct is added to the link list it is placed int front of
> the link list. This means the last VT in the list is the first VT. Now
> when a keyboard is detected it scans the VT list from the head to the end. 
> That is why the no console error. I will work on the problem right now.
> 

-- 
Vojtech Pavlik
SuSE Labs

Re: HID stuff broken.

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

> Umm, I think I have just one keyboard. But at the time of the error
> message the keyboard probably wasn't connected, being USB and with my
> bad USB active extension cable, which needs to be unplugged and
> replugged after each boot to detect the devices on it.
> 
> So it's one-display-no-keyboard case. It works fine with 2.4.14-ruby.

Hm. This must be due to my VT creation changes. A tty is registered when
it detects a keyboard and their is a VT display with no keyboard attached. 

   I just realized their is the other issue I have to fix. That is the
/dev/console redirect thing. Right now this is really broken. For example
for the LP console their is no tty related to it. So if you attempt to
open /dev/console for a LP console it bombs. So I have been working on a
/dev/console that registers it own TTY that wraps aroung the struct
console functions. This will solve alot of problems.
   At present this affects the situation where you have no keyboard plugged 
in at boot time but after boot time you plug it in. Now the console stuff
can exist without a TTY. I reworked the code that way. Unfortunely the
other way around doesn't quite work yet. I'm working on the new /dev/console
TTY driver today. This way their will be no keyboard problems in the
future. /dev/console will be such that it doesn't matter if you have no
way to bring input in (i.e no keyboard). As for /dev/ttyX this will not be
the case.