linux-kernel - Re: factor out common s2ram wakeup code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4796519C.6040501@zytor.com>
Date:	Tue, 22 Jan 2008 12:27:08 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Pavel Machek <pavel@....cz>
CC:	"Rafael J. Wysocki" <rjw@...k.pl>,
	kernel list <linux-kernel@...r.kernel.org>, mingo@...hat.com,
	tglx@...utronix.de
Subject: Re: factor out common s2ram wakeup code

Pavel Machek wrote:
> It seems to compile 32/64bit, and work 32bit... Now, video code should
> be probably shared with kernel/boot; but that was rewritten to C and
> I'm not sure if I know enough about linkers... basically the C code
> should replace mode_set() and friends. Peter, can you help?

Yes, absolutely.  I think we should probably segregate out into a 
subdirectory the part of the code that should be run in 16-bit mode, and 
then it's just a matter of pretty much replicating the mechanisms used 
in arch/x86/boot.

How can I best be of help?

	-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/