readme-related files update

STYLE-GUIDELINES-SDL

@@ -0,0 +1,14 @@
+FceuX-SDL Style Guidelines
+=========================
+Background
+----------
+While having style guidelines specific to a directory in a sourcetree is slightly riddiculous, fceuX has a unique elaborate history of the code.  I (prg318) have ressurected the majority of the SDL port code and tried to keep some aspects of the style consistant (although not many aspects were that consistent to begin with due to the amount of different people who have contributed to this codebase). Much of the SDL code is compliant to these guidelines so please use this guidelines when going forth and making contributions in src/drivers/sdl. 
+
+Tabs
+----
+Hard tabs only!  Please!  src/drivers/sdl/* entirely consists of hard tabbed code.  Please continue to use this convention.  Consult the documentation of your text editor documentation for instructions on how to this with your editor.
+
+Return Statements
+-----------------
+Please use the "return 0;" style return statements instead of the "return(0);" style return statements.
+

STYLE-GUIDELINES-SDL.md

@@ -1,14 +0,0 @@
-FceuX-SDL Style Guidelines
-=========================
-Background
-----------
-While you may think having style guidelines specific to a directory in a sourcetree is outrageous, fceuX has a unique elaborate history of the code.  I (prg318) have ressurected the majority of the SDL port code and tried to keep some aspects of the style consistant (although not many aspects were that consistent to begin with due to the amount of different people who have contributed to this codebase).  The SDL port alone consists of over 8,000 lines of C++ code, much of which is compliant to these guidelines so please use this guidelines when going forth and writing code in src/drivers/sdl. *Following these simple rules will make it a lot easier for the developers to accept your patch.*
-
-Tabs
-----
-Hard tabs only!  Please!  src/drivers/sdl/* entirely consists of hard tabbed code.  Please continue to use this convention.  Consult the documentation of your text editor documentation for instructions on how to this with your editor.
-
-Return Statements
------------------
-Please use the "return 0;" style return statements instead of the "return(0);" style return statements.
-

TODO-SDL

@@ -1,6 +1,5 @@
 Features
 ========
-	* autosave/autoload for xbmc
 	* SDL.Vsync
 		* lets wait on this -- theres no simple way to use the OS default in SDL unless we just dont touch it, which might be the best thing to do here.
   
@@ -13,12 +12,11 @@ GTK
 		* scanlines
 	* GUI Cheat editor
 
-SDL 1.3
+SDL 2.0
 =======
 	* segfaults when opening a second game
 	* segfaults on fullscreen entry
-	* havent tested this in a while
+	* has not been tested in a while
-	* not a 2.2.0 target
 
 BUGS
 ====