Removed ban against speed 0 with burn_drive_set_buffer_waiting()

libburn/trunk/cdrskin/cdrskin.1

@@ -829,8 +829,6 @@ Mode 0 disables this feature. Mode -1 keeps it unchanged. Default is:
 modesty_on_drive=0:min_percent=65:max_percent=95
 .br
 Percentages are permissible in the range of 25 to 100.
-This mode can be activated only if option speed= is given with a number > 0
-which should be realistic, i.e. appropriate for drive and media.
 .TP
 .BI \--no_abort_handler
 On signals exit even if the drive is in busy state. This is not a very good

libburn/trunk/cdrskin/cdrskin.c

@@ -2990,8 +2990,7 @@ int Cdrskin_adjust_speed(struct CdrskiN *skin, int flag)
  burn_drive_set_speed(skin->drives[skin->driveno].drive,k_speed,k_speed);
 
 #ifdef Cdrskin_libburn_has_set_waitinG
- if(k_speed>0)
-   modesty= skin->modesty_on_drive;
+ modesty= skin->modesty_on_drive;
  burn_drive_set_buffer_waiting(skin->drives[skin->driveno].drive,
                                modesty, -1, -1, -1,
                                skin->min_buffer_percent,

libburn/trunk/cdrskin/cdrskin_timestamp.h

@@ -1 +1 @@
-#define Cdrskin_timestamP "2007.07.17.085823"
+#define Cdrskin_timestamP "2007.07.19.072434"

libburn/trunk/libburn/libburn.h

@@ -1310,9 +1310,8 @@ void burn_drive_set_speed(struct burn_drive *d, int read, int write);
     This may allow the driver to operate on other devices, e.g. a disk from
     which to read the input for writing. On the other hand, this checking might
     reduce maximum throughput to the drive or even get misled by faulty buffer
-    fill replies from the drive. It is advised not to set speed to 0 (= max)
-    together with enabling buffer waiting.
-    If a setting parameters is < 0, then this setting will stay unchanged
+    fill replies from the drive.
+    If a setting parameter is < 0, then this setting will stay unchanged
     by the call.
     Known burner or media specific pitfalls:
     To have max_percent larger than the burner's best reported buffer fill has