Krzysztof Halasa wrote:
Jan Engelhardt <[EMAIL PROTECTED]> writes:
I checked, and looking at offset 0x497 seems to work fine on a couple of
systems with USB keyboards.
Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
return when there is actually more
Krzysztof Halasa wrote:
Jan Engelhardt [EMAIL PROTECTED] writes:
I checked, and looking at offset 0x497 seems to work fine on a couple of
systems with USB keyboards.
Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
return when there is actually more than
Randy Dunlap wrote:
On Sun, 18 Feb 2007 09:32:15 -0800 H. Peter Anvin wrote:
Jean Delvare wrote:
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need
On Sun, 18 Feb 2007 09:32:15 -0800 H. Peter Anvin wrote:
> Jean Delvare wrote:
> > On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
> >> Jean Delvare wrote:
> >>> On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
> >>> BIOS RAM is mapped at 0x400 so all we need to
On Sun, 18 Feb 2007 17:04:01 +0100 Jean Delvare wrote:
> On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
> > Jean Delvare wrote:
> > > On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
> > > BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
> > >
Jean Delvare wrote:
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset 0x497). This is how Suse's hwinfo does.
Hi Linus,
On Wed, 14 Feb 2007 11:32:34 -0800 (PST), Linus Torvalds wrote:
> On Wed, 14 Feb 2007, Jean Delvare wrote:
> > On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
> > BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
> > RAM (offset 0x497). This is
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
> Jean Delvare wrote:
> > On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
> > BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
> > RAM (offset 0x497). This is how Suse's hwinfo does.
>
> Perhaps
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset 0x497). This is how Suse's hwinfo does.
Perhaps that's
Hi Linus,
On Wed, 14 Feb 2007 11:32:34 -0800 (PST), Linus Torvalds wrote:
On Wed, 14 Feb 2007, Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset 0x497). This is how
Jean Delvare wrote:
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset 0x497). This is how Suse's hwinfo does.
On Sun, 18 Feb 2007 17:04:01 +0100 Jean Delvare wrote:
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset
On Sun, 18 Feb 2007 09:32:15 -0800 H. Peter Anvin wrote:
Jean Delvare wrote:
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one
Randy Dunlap wrote:
On Sun, 18 Feb 2007 09:32:15 -0800 H. Peter Anvin wrote:
Jean Delvare wrote:
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset 0x497). This is how Suse's hwinfo does.
Perhaps that's what Suse does, but the proper address is 0x417.
0x497 is the
Linus Torvalds wrote:
On Wed, 14 Feb 2007, Dax Kelson wrote:
Are there any technical or political reasons why kernel can't change
from "force off" to "Follow BIOS"?
How would you query it? I'm not even 100% sure that you can on all
keyboards. We never query the leds, we always set them. I
Linus Torvalds wrote:
On Wed, 14 Feb 2007, Dax Kelson wrote:
Are there any technical or political reasons why kernel can't change
from force off to Follow BIOS?
How would you query it? I'm not even 100% sure that you can on all
keyboards. We never query the leds, we always set them. I
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset 0x497). This is how Suse's hwinfo does.
Perhaps that's what Suse does, but the proper address is 0x417.
0x497 is the
Jan Engelhardt <[EMAIL PROTECTED]> writes:
>>I checked, and looking at offset 0x497 seems to work fine on a couple of
>>systems with USB keyboards.
>
> Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
> return when there is actually more than one USB keyboard connected
On Wed, 14 Feb 2007 22:58:42 +0100 (MET)
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
> return when there is actually more than one USB keyboard connected at boot.
The BIOS initial numlock value which is a singular
Hi,
On Feb 14 2007 14:34, Dax Kelson wrote:
>
>I checked, and looking at offset 0x497 seems to work fine on a couple of
>systems with USB keyboards.
Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
return when there is actually more than one USB keyboard connected at
On Wed, 2007-02-14 at 11:32 -0800, Linus Torvalds wrote:
>
> On Wed, 14 Feb 2007, Jean Delvare wrote:
> >
> > On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
> > BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
> > RAM (offset 0x497). This is how
On Wed, 14 Feb 2007, Jean Delvare wrote:
>
> On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
> BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
> RAM (offset 0x497). This is how Suse's hwinfo does.
Heh. Shows just how much I ever used DOS and BIOS.
On Wed, 2007-02-14 at 11:12 -0800, Linus Torvalds wrote:
>
> On Wed, 14 Feb 2007, Dax Kelson wrote:
> >
> > Are there any technical or political reasons why kernel can't change
> > from "force off" to "Follow BIOS"?
>
> How would you query it? I'm not even 100% sure that you can on all
>
Hi Linus,
On Wed, 14 Feb 2007 11:12:23 -0800 (PST), Linus Torvalds wrote:
> On Wed, 14 Feb 2007, Dax Kelson wrote:
> > Are there any technical or political reasons why kernel can't change
> > from "force off" to "Follow BIOS"?
>
> How would you query it? I'm not even 100% sure that you can on
On Wed, 2007-02-14 at 11:12 -0800, Linus Torvalds wrote:
>
> On Wed, 14 Feb 2007, Dax Kelson wrote:
> >
> > Are there any technical or political reasons why kernel can't change
> > from "force off" to "Follow BIOS"?
>
> How would you query it? I'm not even 100% sure that you can on all
>
According to the lore(1) the reason that the kernel unconditionally
turns off the num lock was so that Linus' laptop came up ready to type.
The issue is that if you force num lock on, then laptop users are messed
up since for most laptops your keyboard changes as follows:
7890 = 789*
uiop =
On Wed, 14 Feb 2007, Dax Kelson wrote:
>
> Are there any technical or political reasons why kernel can't change
> from "force off" to "Follow BIOS"?
How would you query it? I'm not even 100% sure that you can on all
keyboards. We never query the leds, we always set them. I think. I don't
According to the lore(1) the reason that the kernel unconditionally
turns off the num lock was so that Linus' laptop came up ready to type.
The issue is that if you force num lock on, then laptop users are messed
up since for most laptops your keyboard changes as follows:
7890 = 789*
uiop =
On Wed, 2007-02-14 at 11:12 -0800, Linus Torvalds wrote:
On Wed, 14 Feb 2007, Dax Kelson wrote:
Are there any technical or political reasons why kernel can't change
from force off to Follow BIOS?
How would you query it? I'm not even 100% sure that you can on all
keyboards. We never
On Wed, 14 Feb 2007, Dax Kelson wrote:
Are there any technical or political reasons why kernel can't change
from force off to Follow BIOS?
How would you query it? I'm not even 100% sure that you can on all
keyboards. We never query the leds, we always set them. I think. I don't
know of
Hi Linus,
On Wed, 14 Feb 2007 11:12:23 -0800 (PST), Linus Torvalds wrote:
On Wed, 14 Feb 2007, Dax Kelson wrote:
Are there any technical or political reasons why kernel can't change
from force off to Follow BIOS?
How would you query it? I'm not even 100% sure that you can on all
On Wed, 2007-02-14 at 11:12 -0800, Linus Torvalds wrote:
On Wed, 14 Feb 2007, Dax Kelson wrote:
Are there any technical or political reasons why kernel can't change
from force off to Follow BIOS?
How would you query it? I'm not even 100% sure that you can on all
keyboards. We never
On Wed, 14 Feb 2007, Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset 0x497). This is how Suse's hwinfo does.
Heh. Shows just how much I ever used DOS and BIOS.
But
On Wed, 2007-02-14 at 11:32 -0800, Linus Torvalds wrote:
On Wed, 14 Feb 2007, Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
RAM (offset 0x497). This is how Suse's hwinfo
Hi,
On Feb 14 2007 14:34, Dax Kelson wrote:
I checked, and looking at offset 0x497 seems to work fine on a couple of
systems with USB keyboards.
Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
return when there is actually more than one USB keyboard connected at
On Wed, 14 Feb 2007 22:58:42 +0100 (MET)
Jan Engelhardt [EMAIL PROTECTED] wrote:
Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
return when there is actually more than one USB keyboard connected at boot.
The BIOS initial numlock value which is a singular value.
Jan Engelhardt [EMAIL PROTECTED] writes:
I checked, and looking at offset 0x497 seems to work fine on a couple of
systems with USB keyboards.
Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
return when there is actually more than one USB keyboard connected at boot.
38 matches
Mail list logo
