From: Erwan Velu <erwan@seanodes.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH]: atiixp : Enabling UDMA5 on IXP200
Date: Sat, 22 Oct 2005 09:22:25 +0200 [thread overview]
Message-ID: <4359E8B1.6070905@seanodes.com> (raw)
In-Reply-To: <58cb370e0510131058g23e956a8m7bb0a82d8f670ce6@mail.gmail.com>
Bartlomiej Zolnierkiewicz wrote:
>Hi,
>
>I've seen your patch but I'm still thinking how to solve this problem
>because we can't just check for PCI device ID as it is a PATA controller
>(I guess that there is some PATA-SATA bridge on this particular
>motherboard). One possible fix is to check if device is SATA using
><linux/ata.h>:ata_id_is_sata() but I don't know how reliable it is,
>I need to check both ATA and SATA specs).
>
>
Did you had any ideas on how to continue for fixing this issues with the
atiixp 200 chipset ?
prev parent reply other threads:[~2005-10-22 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 12:02 [PATCH]: atiixp : Enabling UDMA5 on IXP200 Velu Erwan
2005-10-13 15:14 ` Velu Erwan
2005-10-13 17:58 ` Bartlomiej Zolnierkiewicz
2005-10-14 3:47 ` Erwan Velu
2005-10-22 7:22 ` Erwan Velu [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=4359E8B1.6070905@seanodes.com \
--to=erwan@seanodes.com \
--cc=bzolnier@gmail.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).