linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jason Keltz <jas@cse.yorku.ca>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: ide cdrom problems on new imac
Date: Sat, 7 Jun 2008 11:01:32 +0100	[thread overview]
Message-ID: <20080607110132.30ea73fc@core> (raw)
In-Reply-To: <Pine.LNX.4.63.0806062141280.29139@indigo.cs.yorku.ca>

> When you say "old IDE", can you expand on this one for me.  I'm trying to 
> learn as I go along.  This is the old Linux IDE driver with support of an 
> Intel PIIX module?  If I understand it correctly, why would RedHat then 

drivers/ide is the old IDE driver which is pretty much for parallel ATA
(big cables) not serial ATA.

> update the PIIX module to support later versions of the Intel chipsets, if 
> this can't work properly with the older version of the kernel?

The bug only shows up on the Mac in specific cases so nobody discovered
it before then.

> Yes, as far as I can tell 5.x doesn't do it either.  I guess I have to 
> wait for CentOS 6, or go with a distribution like Ubuntu that uses a more 
> up to date kernel as a start.

Any distro which tracks recent kernels should work fine so Ubuntu,
Fedora etc. Centos/RHEL/etc backport minimal fixes to old kernels to keep
maximum stability. The Intel chipset bug might get fixed in an update in
future. but I couldn't say.

> > You need to use the current IRQ clearing logic for both drivers - the old
> > logic only clears the ata status register on PIO events, the newer one
> > clears both the ata and DMA status to work around the Intel funny.
> 
> And I guess it wouldn't be easy for me to make these changes, especially 
> without much kernel hacking knowledge?

It's not that big from what I remember, I don't know if Jeff has the
relevant patch to hand ?

> > [By a strict reading of the spec the Intel behaviour does appear allowed,
> > although I hope Intel didn't intend it ...]
> 
> Has anyone tried to contact Intel to see their response? 

I've not pursued it - even if it wasn't intentional it won't get fixed so
we need to support it and now do.

Alan

      reply	other threads:[~2008-06-07 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 17:16 ide cdrom problems on new imac Jason Keltz
2008-06-06 20:49 ` Alan Cox
2008-06-07  1:48   ` Jason Keltz
2008-06-07 10:01     ` Alan Cox [this message]

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=20080607110132.30ea73fc@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jas@cse.yorku.ca \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).