From: Tian Kevin [EMAIL PROTECTED]
Register %ebx serves as the global offset table base register
for position-independent code. For absolute code, %ebx serves
as a local register and has no specified role in the function
calling sequence. In either case, a function must preserve the
register
Hi!
From: Tian Kevin [EMAIL PROTECTED]
Register %ebx serves as the global offset table base register
for position-independent code. For absolute code, %ebx serves
as a local register and has no specified role in the function
calling sequence. In either case, a function must preserve the
According to the SYSTEM V APPLICATION BINARY INTERFACE,
Intel386 Architecture:
ecx and edx: Scratch registers have no specified role in the standard calling
sequence. Functions do not have to preserve their values for the
caller.
Best regards,
Zhang.Rui(Ray)
-Original Message-
From:
Hi all,
Here is a list of some known regressions in 2.6.22-rc3.
Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions
Unclassified
Subject: build failed in function `vic_sys_interrupt'
References : http://lkml.org/lkml/2007/5/31/227
Submitter :
On Fri, Jun 01, 2007 at 12:37:58AM -0400, Dmitry Torokhov wrote:
On Friday 01 June 2007 00:08, Matthew Garrett wrote:
If you let users alter the kernel keymap, then you need to implement
support for resetting the kernel keymap on exit. Otherwise it's a
trivial DoS.
You already do -
On Thu, 2007-05-31 at 12:49 -0400, Len Brown wrote:
The name of this patch is really split ACPI function tracing
out of CONFIG_ACPI_DEBUG to a new Kconfig build option
I agree that tracing should be its own build option.
Thanks.
I don't agree that enabling CONFIG_ACPI_DEBUG by default
is
On 6/1/07, Matthew Garrett [EMAIL PROTECTED] wrote:
On Fri, Jun 01, 2007 at 12:37:58AM -0400, Dmitry Torokhov wrote:
On Friday 01 June 2007 00:08, Matthew Garrett wrote:
If you let users alter the kernel keymap, then you need to implement
support for resetting the kernel keymap on exit.
On Fri, Jun 01, 2007 at 10:04:56AM -0400, Dmitry Torokhov wrote:
Anyway, I think that we don't want ordinary users to alter hardware
keymapping, it should indeed be priveleged operation done by box's
administrator. Hopefully the infrastructure (hal/udev/whatever) will
be able to load proper
On Fri, 01 Jun 2007, Matthew Garrett wrote:
On Thu, May 31, 2007 at 11:33:10PM -0400, Dmitry Torokhov wrote:
On Thursday 31 May 2007 21:44, Matthew Garrett wrote:
It's not trivial at all. You need to introduce a mechanism for noting a
KEY_UNKNOWN keypress. It then needs to signal the
On Fri, 01 Jun 2007, Matthew Garrett wrote:
Or we could just leave the mapping up to individual users, which avoids
the problem.
Other than the fact that it is not a piece of candy to implement correctly.
Again, it is not only about X. What if X is not running (or running but
nobody is
On Fri, 01 Jun 2007, Dmitry Torokhov wrote:
On 6/1/07, Matthew Garrett [EMAIL PROTECTED] wrote:
What I am trying to say - there already EVIOCSKEYCODE ioctl in the
kernel. And for force feedback devices to work you need to nable
writing to corresponding /dev/input/eventX thus opening
On 6/1/07, Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote:
On Fri, 01 Jun 2007, Dmitry Torokhov wrote:
On 6/1/07, Matthew Garrett [EMAIL PROTECTED] wrote:
What I am trying to say - there already EVIOCSKEYCODE ioctl in the
kernel. And for force feedback devices to work you need to nable
Hi Richard,
On 5/31/07, Richard Hughes [EMAIL PROTECTED] wrote:
On Thu, 2007-05-31 at 14:44 +0100, Richard Hughes wrote:
Nope, impossible AFAICS. The hardware is just broken. Windows XP has an
toshiba supplied daemon that polls, so I think we have to just bite the
bullet.
... adding in
Hi,
resume from suspend to ram doesn't work for my laptop and never
has. So, this is not a regression.
Hibernate (aka suspend to disk) works, however.
When I resume, everything seems to come up (fan becomes busy, disk and
dvd spin up for a short time), but the machine is not responding to
On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
Hi,
resume from suspend to ram doesn't work for my laptop and never
has. So, this is not a regression.
Hibernate (aka suspend to disk) works, however.
When I resume, everything seems to come up (fan becomes busy, disk and
dvd spin up
Rafael J. Wysocki [EMAIL PROTECTED] writes:
On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
When I resume, everything seems to come up (fan becomes busy, disk and
dvd spin up for a short time),
Hmm, what about the screen?
When the laptop is dead, screen remains black.
When I skip
On Friday 01 June 2007 14:20:44 Michal Piotrowski wrote:
Networking
Subject: b44: regression in 2.6.22
References : http://lkml.org/lkml/2007/5/27/108
Submitter : Maximilian Engelhardt [EMAIL PROTECTED]
Handled-By : Michael Buesch [EMAIL PROTECTED]
Well, it looks like a highres-timers
On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
Rafael J. Wysocki [EMAIL PROTECTED] writes:
On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
When I resume, everything seems to come up (fan becomes busy, disk and
dvd spin up for a short time),
Hmm, what about the screen?
When
On Thu, May 31, 2007 at 12:37:06AM -0400, Len Brown wrote:
Logistics:
Monday, June 25th
Tuesday, June 26th
We have the Garden Suite in Les Suites Ottawa at our disposal 9AM - 6PM
(thanks Intel).
The room has 20 seats. It also has natural light:-)
Format:
Hopefully small enough
Rafael J. Wysocki [EMAIL PROTECTED] writes:
On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
Rafael J. Wysocki [EMAIL PROTECTED] writes:
On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
When I resume, everything seems to come up (fan becomes busy, disk and
dvd spin up for a short
On Saturday, 2 June 2007 00:17, Olaf Dietsche wrote:
Rafael J. Wysocki [EMAIL PROTECTED] writes:
On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
Rafael J. Wysocki [EMAIL PROTECTED] writes:
On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
When I resume, everything seems to come
On Sat, June 2, 2007 00:17, Olaf Dietsche wrote:
It doesn't work. I tried all options s2ram -f (-s, -p, -m, -r, -a 1, -a 2,
-a 3) one after the other.
Since the screen (or any other device) works without problems, when I
skip acpi_enter_sleep_state(), I don't think it's screen related.
I use
_OSI(Linux) is like _OS(Linux), it is ill-defined and
virtually no BIOS vendors test interaction with it.
As a result, it can do more damage than good because
it causes the BIOS to follow un-tested paths.
Recently, several machines have turned up that erroneously
test this string in a way which
23 matches
Mail list logo
