Hello!
On Tue, 26 Dec 2006, Luigi Rizzo wrote:
I suggest the following two fixes:
1. change burncd.c as below, so that if CDRIOCGETPROGRESS does not return
anything good, it calls CDIOCRESET to determine when the command
is complete.
This can be improved by calling CDIOCRESET
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x changes in two places:
* the ioctl handler, acd_get_progress() in /sys/dev/ata/atapi-cd.c
Luigi Rizzo [EMAIL PROTECTED] writes:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
[ .. stuff deleted .. ]
Patches below (to be
Luigi Rizzo wrote:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x changes in two places:
* the ioctl handler, acd_get_progress() in
On Wed, Dec 27, 2006 at 02:33:15AM +0100, Søren Schmidt wrote:
Luigi Rizzo wrote:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x