[Libburn] libburn_drive_get_busy get's locked

Derek Foreman manmower@signalmarketing.com
Wed, 3 Dec 2003 20:41:58 -0600 (CST)


On Wed, 3 Dec 2003, Derek Foreman wrote:

> On Thu, 4 Dec 2003, Tiago Cogumbreiro wrote:
>
> > I am testing the changes to making possible to get the progress while
> > blanking the media, unfornatly after i call libburn_drive_get_busy it
> > locks until i the cd is fully blanked thus making impossible to test the
> > progress, did i do anything wrong?
>
> libburn_drive_get_busy should definately _not_ locking...
>
> oh, I think I know what it is.  your call in drive.c blocks because the
> drive is still frozen in my sync blank code.  maybe there's just a flag
> I've set wrong cuz I wanted it to block.  I'll check it.

confirmed, I don't set the immediate bit in my mmc_erase call.

but just changing that to 1 isn't the answer, because the erase thread
will return success immediately, and we want it to remain until the
command is completely finished.