next problem: keyboard.

[Ronald G Minnich]

so, no keyboard I/O. But I am setting the bit in the PIIX4E register to
enable KBBCS#. The new hunt begins ....

ron

-
To unsubscribe: send mail to [e-mail]
with 'unsubscribe openbios' in the body of the message

[fb-d] next problem: keyboard.

[Jeff Garzik]

Ronald G Minnich wrote:
> so, no keyboard I/O. But I am setting the bit in the PIIX4E register to
> enable KBBCS#. The new hunt begins ....

What are the symptoms of the failure?  Does the Linux kernel print out
any keyboard-related messages?   Does booting even get far?

Also, do you have a link to the L440GX mobo databook and the SIS
databook, so I can take a peek and perhaps give more informed guesses
about what to try next :)

Jeff

[fb-d] next problem: keyboard.

[Ronald G Minnich]

On Thu, 4 May 2000, Jeff Garzik wrote:
> Ronald G Minnich wrote:
> What are the symptoms of the failure?  Does the Linux kernel print out
> any keyboard-related messages?   Does booting even get far?

The kernel is up with a login prompt, displaying very nicely on the Matrox
(cool logo in the upper left, BTW). When it tries to do anything with the
keyboard, however, nothing happens.

Turns out that you have to do a bit of work with the PIIX4E power
management registers to get things like keyboard going. I'm still digging.

docs: SiS not on the web yet. They will be happy to send docs, however,
those guys are really cool. For Intel, I will try to remember the links,
but at the least you need the PIIX4E manual.

ron

-
To unsubscribe: send mail to [e-mail]
with 'unsubscribe openbios' in the body of the message

[fb-d] next problem: keyboard.

[Jeff Garzik]

Ronald G Minnich wrote:
> On Thu, 4 May 2000, Jeff Garzik wrote:
> > Ronald G Minnich wrote:
> > What are the symptoms of the failure?  Does the Linux kernel print out
> > any keyboard-related messages?   Does booting even get far?
>
> The kernel is up with a login prompt, displaying very nicely on the Matrox
> (cool logo in the upper left, BTW). When it tries to do anything with the
> keyboard, however, nothing happens.
>
> Turns out that you have to do a bit of work with the PIIX4E power
> management registers to get things like keyboard going. I'm still digging.
>
> docs: SiS not on the web yet. They will be happy to send docs, however,
> those guys are really cool. For Intel, I will try to remember the links,
> but at the least you need the PIIX4E manual.

I've got the PIIX4* manuals, so all I would need is the
southbridge/northbridge databooks.  Those are the ones which IMHO may be
more important to getting keyboard going than the PIIX4 manual...

Comments from the PIIX4 manual:

* The PM registers relating to keyboard are probably red herrings -- it
appears you are only signalling that keyboard events should generate PM
event interrupts, which isn't what you are looking for
* The Fast A20 bit (bit 1 of port 92 register) is logically combined
with the input from the keyboard controller. (x-bus interface, a20gate
signal)  maybe that is significant, maybe not.
* have you enabled X-BUS accesses (function 0, register XBCS 0x4E-4F)
* have you enabled the keyboard interrupt?
* have you cleared the kbd interrupts (RIRQ, 0x60)
* is the USB keyboard interface "stealing" the keyboard port for
itself?  (register C0-C1)
* port 92 (P92) register mentions keyboard
* possibly important bits:  keyboard bit on DEVRESA register (function
3, bit 28, register offset 0x5C-5F) and DEVRESB register (function 3,
bit 30, register offset 0x60-63)

[fb-d] next problem: keyboard.

[Ronald G Minnich]

On Thu, 4 May 2000, Jeff Garzik wrote:
> The PM registers relating to keyboard are probably red herrings -- it
>
> appears you are only signalling that keyboard events should generate PM
> event interrupts, which isn't what you are looking for

yes, right, I said 'PM' but should have said 'function 3'
> The Fast A20 bit (bit 1 of port 92 register) is logically combined
>
> with the input from the keyboard controller. (x-bus interface, a20gate
> signal)  maybe that is significant, maybe not.

I never thought A20 mattered except for real mode addressing, am I missing
something here.
> have you enabled X-BUS accesses (function 0, register XBCS 0x4E-4F)

yes
> have you enabled the keyboard interrupt?

hmmm ... I'm still now sure how the heck I do this! Maybe the 'steenking
bios' code that programs the 8259s?
> have you cleared the kbd interrupts (RIRQ, 0x60)

I put this in just now.
> is the USB keyboard interface "stealing" the keyboard port for
>
> itself?  (register C0-C1)

I don't think so. It defaults to 0 (Intel does manage to get "defaults to
0" right much of the time) ...
> port 92 (P92) register mentions keyboard

This is the gross a20m# garbage, I don't think it affects us, but ...
> possibly important bits:  keyboard bit on DEVRESA register (function
>
> 3, bit 28, register offset 0x5C-5F) and DEVRESB register (function 3,
> bit 30, register offset 0x60-63)

yes, I have these on. These are what I called "PM" registers.

I'm going to try out the little loop that OpenBIOS uses for keyboard init
and see if I get anywhere.

thanks

ron

-
To unsubscribe: send mail to [e-mail]
with 'unsubscribe openbios' in the body of the message

[fb-d] next problem: keyboard.

[Jeff Garzik]

The PC-AT Boot Process and Option ROMs
http://developer.intel.com/update/departments/servers/sv09991a.htm

[fb-d] next problem: keyboard.

[Jeff Garzik]

One more link...   BIOS-level code from Intel!  :)
http://developer.intel.com/design/intarch/SWSUP/

[fb-d] next problem: keyboard.

[Konstantin Zhidkov]

May be the keyboard initialization code from OpenBIOS will help? Keyboard
works well with OpenBIOS on my L440GX+.

Konstantin

Ronald G Minnich wrote:
> so, no keyboard I/O. But I am setting the bit in the PIIX4E register to
> enable KBBCS#. The new hunt begins ....
>
> ron
>
> Freebios-devel mailing list
> [e-mail]
> http://lists.sourceforge.net/mailman/listinfo/freebios-devel

-
To unsubscribe: send mail to [e-mail]
with 'unsubscribe openbios' in the body of the message

[fb-d] next problem: keyboard.

[Ronald G Minnich]

On Fri, 5 May 2000, Konstantin Zhidkov wrote:
> May be the keyboard initialization code from OpenBIOS will help? Keyboard
> works well with OpenBIOS on my L440GX+.
>
> Konstantin

yes but are you running out of NVRAM? if you are just loading openbios
with the bios loader (i.e. under DOS) than things will work that won't
work from a "cold" machine.

That said I'll yank down the newest openbios and see what's up.

ron

-
To unsubscribe: send mail to [e-mail]
with 'unsubscribe openbios' in the body of the message

[fb-d] next problem: keyboard.

[Konstantin Zhidkov]

Ronald G Minnich wrote:
> On Fri, 5 May 2000, Konstantin Zhidkov wrote:
> > May be the keyboard initialization code from OpenBIOS will help? Keyboard
> > works well with OpenBIOS on my L440GX+.
> >
> > Konstantin
>
> yes but are you running out of NVRAM? if you are just loading openbios
> with the bios loader (i.e. under DOS) than things will work that won't
> work from a "cold" machine.

I'm running out of NVRAM, but after hardware reset. I'm not running after
power up, because I can't program SDRAM mode register.
> That said I'll yank down the newest openbios and see what's up.
>
> ron
>
> Freebios-devel mailing list
> [e-mail]
> http://lists.sourceforge.net/mailman/listinfo/freebios-devel

-
To unsubscribe: send mail to [e-mail]
with 'unsubscribe openbios' in the body of the message