All of lore.kernel.org
 help / color / mirror / Atom feed
From: Domenico Andreoli <cavok@libero.it>
To: Bas Vermeulen <bvermeul@blackstar.nl>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>,
	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 18:34:22 +0200	[thread overview]
Message-ID: <20050715163422.GA1867@raptus.dandreoli.com> (raw)
In-Reply-To: <1121421557.5110.11.camel@laptop.blackstar.nl>

On Fri, Jul 15, 2005 at 11:59:17AM +0200, Bas Vermeulen wrote:
> On Fri, 2005-07-15 at 11:31 +0200, Carl-Daniel Hailfinger wrote:
> > Hi Jeff,

hi all,

> > 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 also have a ICH6M. the SATA HD is correctly seen and used but the
cdrom unit isn't. i'm using a vanilla 2.6.12.2.

> 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

it works! i'm now able to read and write cdroms :)

> Suse has probably done that for you, it's disabled by default.

why it is disabled by default? what do these macros mean? what is
really happening? thank you.

cheers
domenico

-----[ Domenico Andreoli, aka cavok
 --[ http://people.debian.org/~cavok/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

  parent reply	other threads:[~2005-07-15 16:34 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
2005-07-15 12:08     ` Bas Vermeulen
2005-07-15 16:34   ` Domenico Andreoli [this message]
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=20050715163422.GA1867@raptus.dandreoli.com \
    --to=cavok@libero.it \
    --cc=bvermeul@blackstar.nl \
    --cc=c-d.hailfinger.devel.2005@gmx.net \
    --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 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.