From owner-freebsd-multimedia  Mon Apr 30  8:37:58 2001
Delivered-To: freebsd-multimedia@freebsd.org
Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114])
	by hub.freebsd.org (Postfix) with ESMTP id 87E7C37B423
	for <freebsd-multimedia@FreeBSD.ORG>; Mon, 30 Apr 2001 08:37:54 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.11.3/8.11.3) id f3UFboY81387;
	Mon, 30 Apr 2001 17:37:50 +0200 (CEST)
	(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <200104301537.f3UFboY81387@freebsd.dk>
Subject: Re: Problems with burncd on CURRENT
In-Reply-To: <20010430161145.C65506@orac.frost.net> "from Matthew Frost at Apr
 30, 2001 04:11:45 pm"
To: Matthew Frost <matthewf@orac.frost.net>
Date: Mon, 30 Apr 2001 17:37:50 +0200 (CEST)
Cc: freebsd-multimedia@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL88 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-freebsd-multimedia@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

It seems Matthew Frost wrote:
> > > could it be the MFC to acd_close_disk for multisession support that's
> > > making it not work.  Presumably it's the mode select failing before
> > > the ATAPI_CLOSE_TRACK happens?
> > 
> > According to the research I've done that seems not to be the case,
> > atl least not for all drives...
> 
> Oh well.
> 
> Is there anything you can tell me about what information you would
> need to get this drive going (so I can try talking to Yamaha about
> getting the correct info).

I need the specs that tells how and what of the MMC spec they
implemented.

> I presume this is some kind of drive quirk that has to be coped with,
> if so, I take it that people writing Windows based burning software
> will have the same problems in supporting drives unless they can get
> documentation? 

Exactly.

-Søren

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-multimedia" in the body of the message