All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: "Andre Hedrick" <andre@linux-ide.org>,
	"Brian Gerst" <bgerst@didntduck.org>
Cc: "Christian Borntraeger" <linux@borntraeger.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: ide-related kernel panic in 2.4.19 and 2.4.20-pre11
Date: Mon, 21 Oct 2002 00:54:30 +0200	[thread overview]
Message-ID: <20021020225430.11019@192.168.4.1> (raw)
In-Reply-To: <Pine.LNX.4.10.10210191627090.24031-100000@master.linux-ide.org>

>Asking me to make it so you or anyone else can bypass
>copy-content-protection is out of the question.  If you do not ask the
>device to do bad things, then it will not do bad things back at you.

Andre, your argument is pointless, the right answer is indeed
what you wrote below, that is don't buy those ;) Though still,
I agree we shouldn't oops.

Also one problem here is that machines like all new macs can only
_play_ CDs by reading their audio datas via ATAPI and sending those
to the sound chip, they have no analog output on the drive and
if they had, Apple didn't wire it to the sound chip.
So on these configs, there is nothing wrong even in the US wanting
to _play_ a CD you have legally purchased...

Trying to do that shouldn't result into a kernel oops :)

So the point is that even if the drive fucks up, it should
be possible to not crash, detect the fuckup, error the read
request (at least), and eventually reset the drive if it
needs that to be put back in a sane state.

I don't know what exactly is going on at the transport level
with those so-called "copy protected" CDs though, I'm afraid
only you knows exactly what's up there ;) I could investigate,
but I have no intend spending money on a copy-protected CD :)

>If your memory is short, recall I was the only person to stand up and take
>issue about having CPRM stuffed into your harddrives by default.
>
>Make a note, DON"T BUY SONY CDRW Products. 
>
>Now if you are serious about want to fix the issue and not rant about
>issues that have no meaning because they are your opinion on how the world
>should work as it relates to hardware, then we can move on.



  parent reply	other threads:[~2002-10-20 20:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19 19:41 PROBLEM: ide-related kernel panic in 2.4.19 and 2.4.20-pre11 Christian Borntraeger
2002-10-19 22:02 ` Andre Hedrick
2002-10-19 22:32   ` Andreas Steinmetz
2002-10-19 22:49     ` Andre Hedrick
2002-10-21 12:22     ` Alan Cox
2002-10-19 22:39   ` Brian Gerst
2002-10-19 22:54     ` Andre Hedrick
2002-10-19 23:19       ` Brian Gerst
2002-10-19 23:44         ` Andre Hedrick
2002-10-20  0:14           ` Brian Gerst
2002-10-20  0:41             ` Andre Hedrick
2002-10-20 15:46               ` Denis Vlasenko
2002-10-20 14:59           ` Henning P. Schmiedehausen
2002-10-20 22:54           ` Benjamin Herrenschmidt [this message]
2002-10-19 23:20       ` Toon van der Pas
2002-10-20  0:01         ` Andre Hedrick
2002-10-20 15:01           ` Henning P. Schmiedehausen
2002-10-20 10:14   ` Christian Borntraeger
2002-10-20 22:49   ` Bill Davidsen
2002-10-31 22:00     ` Thomas Dodd
2002-11-01  1:24       ` Bill Davidsen
2002-10-20 23:01   ` David Woodhouse

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=20021020225430.11019@192.168.4.1 \
    --to=benh@kernel.crashing.org \
    --cc=andre@linux-ide.org \
    --cc=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@borntraeger.net \
    /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.