cdrdao-devel

[Cdrdao-devel] MMC autodetect patch

[Denis L. <den...@ya...>]

I'd like to check in this patch to allow autodetection of an
MMC-compliant device. This does in effect make the '--driver
generic-mmc' optional, or rather, the default value. Note the --driver
option still has precedence, the MMC probe code is only called if no
--driver was specified (and no entry was found in the drivers file).

The probe works by doing a MODE SENSE(10) command (group 1 command
0x5A) to read the CD capabilities (that's what cdrecord does when you
do cdrecord --prcap).

Comments ?

-denis

Re: [Cdrdao-devel] MMC autodetect patch

[Eric B. <eri...@ya...>]

Denis Leroy wrote:

>I'd like to check in this patch to allow autodetection of an
>MMC-compliant device. This does in effect make the '--driver
>generic-mmc' optional, or rather, the default value. Note the --driver
>option still has precedence, the MMC probe code is only called if no
>--driver was specified (and no entry was found in the drivers file).
>
>The probe works by doing a MODE SENSE(10) command (group 1 command
>0x5A) to read the CD capabilities (that's what cdrecord does when you
>do cdrecord --prcap).
>
>Comments ?
>
>  
>
Thank you! This will be a big help.

Re: [Cdrdao-devel] MMC autodetect patch

[Denis L. <den...@ya...>]

This patch has been checked in.

--- Denis Leroy <den...@ya...> wrote:
> I'd like to check in this patch to allow autodetection of an
> MMC-compliant device. This does in effect make the '--driver
> generic-mmc' optional, or rather, the default value. Note the
> --driver
> option still has precedence, the MMC probe code is only called if no
> --driver was specified (and no entry was found in the drivers file).
> 
> The probe works by doing a MODE SENSE(10) command (group 1 command
> 0x5A) to read the CD capabilities (that's what cdrecord does when you
> do cdrecord --prcap).
> 
> Comments ?
> 
> -denis
> 

> ATTACHMENT part 2 application/octet-stream name=mmc2.patch