Re: cdrecod and profile 0x40 (BD-ROM): -atip exits with 255
Giulio Orsero <giulioo@gmail.com> wrote:
> On Wed, 12 Nov 2008 19:25:06 +0100, Joerg.Schilling@fokus.fraunhofer.de
> (Joerg Schilling) wrote:
>
> >Giulio Orsero <giulioo@gmail.com> wrote:
> >
> >> OS: LINUX kernel 2.4.33
> >> USB Blu-ray writer.
> >> == cdrecord command
> >> cdrecord-2.01.01a53 dev=1,0,0 -atip -v
> >> echo "EXIT CODE: $?"
> >>
> >> == cdrecord output
> >...
> >> Current: BD-ROM
> >...
> >> cdrecord-2.01.01a53: Found unsupported 0x40 profile. <===========
> >> cdrecord-2.01.01a53: Sorry, no supported CD/DVD/BD-Recorder found on this
> >> target.
> >> EXIT CODE: 255
> >>
> >
> >I received this messasage already from another person. It looks like a GCC bug.
> >Did you try to compile cdrecord with Sun Studio?
> >Check drv_mmc.c
>
> I checked drv_mmc.c and I see it handles >=0x40, then I grepped for "Found
> unsupported" and added customized messages to distinguish between drv_mmc.c
> and drv_bd.c and I see the error comes from drv_bd.c, not drv_mmc.
>
> == it seems dvr_bd.c does not handle 0x40/0x0040
> if (profile == 0x0043) {
> dp = &cdr_bdre;
> } else if ((profile == 0x0041) || (profile == 0x0042)) {
> dp = &cdr_bdr;
> } else {
> errmsgno(EX_BAD, "Found unsupported 0x%X profile.\n",
> profile);
> return ((cdr_t *)0);
> }
> ===
Thank you!
Strange I thought that I checked for that string and only found it in drv_mmc.c
Jörg
--
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Reply to: