From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alek Du <alek.du@intel.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
rob.rhoads@intel.com
Subject: Re: [PATCH] ata: Add Intel SCH PATA support (revised)
Date: Wed, 30 Apr 2008 15:17:18 +0400 [thread overview]
Message-ID: <4818553E.6040606@ru.mvista.com> (raw)
In-Reply-To: <20080430104931.3aaab288@dxy.sh.intel.com>
Hello.
Alek Du wrote:
>> NAK this patch completely -- both libata and IDE parts.
In the future it would be worth to post 2 separate patches, one for IDE and
one for libata -- since they should go thru the different maintainer trees.
>> Luckily, I have just had a quick look at the datasheet to which you've
>>linked and that was enough to conclude that SCH is *not* compatible to
>>ICH/PIIX family, so absolutely needs a separate driver!
> Most registers are same
Well, if you mean the standard BMDMA and standard PCI config. space
registers (0x00 thru 0x3f), then those are mostly the same for the majority of
the PCI IDE controllers. Why not stick your code into one of the other driver
instead? ;-)
> except for port enable bit, IOCFG and DMA timing. Now
And also PIO and UDMA timings/enable. Actually, all the vendor-specific
PCI config. registers are different from PIIX/ICH -- and that's what makes the
PATA drivers different from each other.
> I know why my patch just works -- the BIOS set the timing correctly.
Yeah, and we have the special drivers which rely on the BIOS doing all the
mode programming...
> Thanks for point this out. I will post a separate driver patch later.
In the meantwhile the only viable solution would be to stick your code
into drivers/ide/pci/generic.c and drivers/ata/ata_generic.c. No more hacks,
please. :-)
> Thanks,
> Alek
MBR, Sergei
next prev parent reply other threads:[~2008-04-30 11:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 6:00 [PATCH] ata: Add Intel SCH PATA support Alek Du
2008-04-26 9:30 ` Alan Cox
2008-04-26 23:51 ` Alek Du
2008-04-27 8:34 ` Alan Cox
2008-04-27 14:03 ` Alek Du
2008-04-27 14:31 ` Alan Cox
2008-04-28 1:20 ` Alek Du
2008-04-28 9:16 ` Alan Cox
2008-04-29 17:22 ` Sergei Shtylyov
2008-04-28 4:05 ` [PATCH] ata: Add Intel SCH PATA support (revised) Alek Du
2008-04-28 8:41 ` Alan Cox
2008-04-28 9:07 ` Alek Du
2008-04-28 9:21 ` Alan Cox
2008-04-28 19:01 ` Bartlomiej Zolnierkiewicz
2008-04-29 0:14 ` Alek Du
2008-04-29 3:41 ` Alek Du
2008-04-29 3:39 ` Alek Du
2008-04-29 16:38 ` Sergei Shtylyov
2008-04-30 2:49 ` Alek Du
2008-04-30 11:17 ` Sergei Shtylyov [this message]
2008-04-26 16:46 ` [PATCH] ata: Add Intel SCH PATA support Sergei Shtylyov
2008-04-26 23:32 ` Alek Du
2008-04-26 23:50 ` Alan Cox
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=4818553E.6040606@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alek.du@intel.com \
--cc=bzolnier@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rob.rhoads@intel.com \
/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).