linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Vincent Bernat <Vincent.Bernat@wallix.com>,
	linux-ide@vger.kernel.org,
	JF Taltavull <jean-francois.taltavull@wallix.com>
Subject: Re: SATA update in 2.4, ICH8
Date: Tue, 26 Jun 2007 09:37:10 -0400	[thread overview]
Message-ID: <46811686.6050408@garzik.org> (raw)
In-Reply-To: <20070626120904.GD23524@1wt.eu>

Willy Tarreau wrote:
> On Mon, Jun 25, 2007 at 10:06:47AM +0200, Vincent Bernat wrote:
>> OoO En  ce début de soirée du  vendredi 22 juin 2007,  vers 21:13, Willy
>> Tarreau <w@1wt.eu> disait:
>>
>>>> This is a SATA CDROM. There is no PATA controller on the motherboard.
>>> I've never tested any SATA CDROM yet. I don't even know if they work with
>>> 2.4 libata. So most likely you have more experience than me in this area.
>>> If you have any other SATA controller on another machine on which you would
>>> test the drive, it could help up determine whether it's the CDROM which is
>>> causing the trouble or this specific controller+driver combination.
>> With an ICH7 controller, CDROM is not working.
> 
> OK, so the problem is not specific to your change, but rather to the driver or
> something else. I have nothing against merging your PCI id update in principle.
> I also have another minor SATA update pending.
> 
> Jeff, if you have any objection, it's the moment !

Any chance you could email me what is pending?

	Jeff




  reply	other threads:[~2007-06-26 13:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21  7:41 SATA update in 2.4, ICH8 Vincent Bernat
2007-06-21 18:21 ` Willy Tarreau
2007-06-22  6:29   ` Vincent Bernat
2007-06-22 19:13     ` Willy Tarreau
2007-06-25  8:06       ` Vincent Bernat
2007-06-26 12:09         ` Willy Tarreau
2007-06-26 13:37           ` Jeff Garzik [this message]
2007-06-26 14:02             ` Willy Tarreau
2007-06-22  7:51   ` Vincent Bernat

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=46811686.6050408@garzik.org \
    --to=jeff@garzik.org \
    --cc=Vincent.Bernat@wallix.com \
    --cc=jean-francois.taltavull@wallix.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=w@1wt.eu \
    /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).