It causes issues in 1st stage access to kdbg. Simply speaking, instead of using vbox window focus to type in kdbg commands, those only work with terminal (like putty) window focus.

2011/3/4 Timo Kreuzer <timo.kreuzer@web.de>

Hmm...

I remember I added it to enable the possibility for backtraces in 1st stage for sysreg. Why does it now cause the opposite? And why is there an inconsistency? In 2nd stage there is an option for debug mode, in 1st stage there is none, so using kdserial (which imo is appropriate way to do it, I always select it) as default is as consistent as using "normal" debug, getting the input from the keyboard driver.

Just my 0,002 ct/kb
Timo


Am 04.03.2011 17:57, schrieb fireball@svn.reactos.org:
Author: fireball
Date: Fri Mar  4 16:57:56 2011
New Revision: 50967

URL: http://svn.reactos.org/svn/reactos?rev=50967&view=rev
Log:
- Revert 47615. Please fix actual sysreg instead of adding inconsistency between 1st, 2nd and 3rd stages debugging connections. This should fix sysreg3's inability to do backtraces.
See issue #5811 for more details.

Modified:
    trunk/reactos/boot/bootdata/txtsetup.sif

Modified: trunk/reactos/boot/bootdata/txtsetup.sif
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/bootdata/txtsetup.sif?rev=50967&r1=50966&r2=50967&view=diff
==============================================================================
--- trunk/reactos/boot/bootdata/txtsetup.sif [iso-8859-1] (original)
+++ trunk/reactos/boot/bootdata/txtsetup.sif [iso-8859-1] Fri Mar  4 16:57:56 2011
@@ -59,7 +59,7 @@
 [SetupData]
 DefaultPath = \ReactOS
 OsLoadOptions = "/NOGUIBOOT /NODEBUG"
-DbgOsLoadOptions = "/NOGUIBOOT /DEBUGPORT=COM1 /FIRSTCHANCE /KDSERIAL"
+DbgOsLoadOptions = "/NOGUIBOOT /DEBUGPORT=COM1 /FIRSTCHANCE"
 ;OsLoadOptions = "/NOGUIBOOT /DEBUGPORT=SCREEN"
 ;OsLoadOptions = "/NOGUIBOOT /DEBUGPORT=BOCHS"






_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev