From: "Thomas Schmitt" <scdbackup@gmx.net>
To: meta-freescale@yoctoproject.org
Cc: wally.yeh@atrustcorp.com
Subject: Re: about freescale dvd-rom
Date: Tue, 19 Aug 2014 11:04:01 +0200 [thread overview]
Message-ID: <23282659961917932173@scdbackup.webframe.org> (raw)
In-Reply-To: <2014081916353221831615@ava.com.cn>
Hi,
first let me state that i am the upstream developer of
libburn, not of cdrtools. :)
Since a few weeks i am watching Lian jianfei's woes with
Linux DVD burning tools.
We used libburn's SCSI logging facility to learn about
the SCSI passthrough traffic between burn program and
DVD drive.
On imx6q board quite frequently, on another ARM based board
much less often, there are glitches to see with the reply
data from the DVD burner.
The imx6q board quite often produces underneath ioctl(SG_IO)
either a userspace SIGSEGV or memory corruption alerts.
But only if board and DVD burner are connected SATA to SATA.
See also
https://lists.yoctoproject.org/pipermail/meta-freescale/2014-July/009648.html
(The suspicion that the correct reply would be put
to the wrong address is disproved meanwhile. The
reply buffer sg_io_hdr_t.dxferp contains all zeros
before ioctl(SG_IO) and non-zero nonsense afterwards.)
All problems vanish, as soon as a SATA-USB bridge is attached
to the DVD burner and the traffic runs over an USB port of
the imx6q board.
I never got reports about such problems with Linux on i386
or amd64. So i assume it has something to do with the SATA
controller on the board and/or the according driver in the
kernel.
Have a nice day :)
Thomas
next prev parent reply other threads:[~2014-08-19 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 7:33 about freescale dvd-rom lianjf
2014-08-19 8:23 ` Wally Yeh
2014-08-19 8:35 ` lianjf
2014-08-19 9:04 ` Thomas Schmitt [this message]
2014-08-19 9:04 ` Wally Yeh
2014-08-19 9:18 ` lianjf
2014-08-19 9:11 ` lianjf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23282659961917932173@scdbackup.webframe.org \
--to=scdbackup@gmx.net \
--cc=meta-freescale@yoctoproject.org \
--cc=wally.yeh@atrustcorp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.