libburnia/libburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Removed ban against speed 0 with burn_drive_set_buffer_waiting()

Browse Source
This commit is contained in:
Thomas Schmitt 2007-07-19 07:23:01 +00:00
parent bdadae6ba5
commit 2c467c8378
4 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cdrskin/cdrskin.1
View File

@ -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 modesty_on_drive=0:min_percent=65:max_percent=95
.br .br
Percentages are permissible in the range of 25 to 100. 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 .TP
.BI \--no_abort_handler .BI \--no_abort_handler
On signals exit even if the drive is in busy state. This is not a very good On signals exit even if the drive is in busy state. This is not a very good

3
cdrskin/cdrskin.c
View File

@ -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); burn_drive_set_speed(skin->drives[skin->driveno].drive,k_speed,k_speed);
#ifdef Cdrskin_libburn_has_set_waitinG #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, burn_drive_set_buffer_waiting(skin->drives[skin->driveno].drive,
modesty, -1, -1, -1, modesty, -1, -1, -1,
skin->min_buffer_percent, skin->min_buffer_percent,

2
cdrskin/cdrskin_timestamp.h
View File

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

5
libburn/libburn.h
View File

@ -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 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 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 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) fill replies from the drive.
together with enabling buffer waiting. If a setting parameter is < 0, then this setting will stay unchanged
If a setting parameters is < 0, then this setting will stay unchanged
by the call. by the call.
Known burner or media specific pitfalls: Known burner or media specific pitfalls:
To have max_percent larger than the burner's best reported buffer fill has To have max_percent larger than the burner's best reported buffer fill has