public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Bas Vermeulen <bvermeul@blackstar.nl>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ATAPI+SATA support in 2.6.13-rc3
Date: Fri, 15 Jul 2005 13:53:53 +0200	[thread overview]
Message-ID: <42D7A3D1.5080609@gmx.net> (raw)
In-Reply-To: <1121421557.5110.11.camel@laptop.blackstar.nl>

Bas Vermeulen schrieb:
> On Fri, 2005-07-15 at 11:31 +0200, Carl-Daniel Hailfinger wrote:
> 
>>Hi Jeff,
>>
>>I have a Intel ICH6M chipset and am using ata_piix as my
>>default disk driver. With the SUSE patched 2.6.11.4 kernel
>>(it has some libata patches) my DVD-RAM drive works, with
>>2.6.13-rc3 it doesn't work. My .config is nearly identical
>>for both kernels (except options introduced after 2.6.11).
>>
>>I have two suspects: the changed interrupt routing and
>>libata version differences. Especially strange is the fact
>>that both kernels seem to disagree with lspci about the
>>interrupts assigned to the SATA controller.
>>
>>Please find dmesg, /proc/interrupts and lspci -v attached
>>for both kernels.
>>
>>Regards,
>>Carl-Daniel
> 
> 
> You'll need to enable ATAPI support for ata_piix in
> include/linux/libata.h
> 
> Change:
> #undef ATA_ENABLE_ATAPI
> 
> into
> #define ATA_ENABLE_ATAPI
> 
> Suse has probably done that for you, it's disabled by default.

Thanks, I'll try that.

Are there any unmerged (in 2.6.13-rc3) libata patches and
where can I find them?

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

  reply	other threads:[~2005-07-15 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-15  9:31 ATAPI+SATA support in 2.6.13-rc3 Carl-Daniel Hailfinger
2005-07-15  9:59 ` Bas Vermeulen
2005-07-15 11:53   ` Carl-Daniel Hailfinger [this message]
2005-07-15 12:08     ` Bas Vermeulen
2005-07-15 16:34   ` Domenico Andreoli
2005-07-15 16:37     ` Jeff Garzik

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=42D7A3D1.5080609@gmx.net \
    --to=c-d.hailfinger.devel.2005@gmx.net \
    --cc=bvermeul@blackstar.nl \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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