mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	albertl@mail.com, Mikael Pettersson <mikpe@it.uu.se>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	alan@redhat.com, Unicorn Chang <uchang@tw.ibm.com>,
	Doug Maxey <dwm@enoyolf.org>
Subject: Re: libata pata_pdc2027x success on sparc64
Date: Wed, 9 Aug 2006 18:15:29 +0200	[thread overview]
Message-ID: <17626.2593.367175.896926@alkaid.it.uu.se> (raw)
In-Reply-To: <44DA07D6.9010101@ru.mvista.com>

Sergei Shtylyov writes:
 > Hello.
 > 
 > Mikael Pettersson wrote:
 > 
 > >  > The libata version has three improvements compared to the IDE version.
 > >  > 
 > >  > 1. The PLL calibration patches in the above URLs (for IDE)
 > >  > still need more improvement as done in the pdc_read_counter()
 > >  > of the libata version.
 > >  > 
 > >  > 2. The Promise 2027x adapters check the "set features - xfer mode"
 > >  >    and set the timing register automatically. However, the automatically
 > >  >    set values are not correct under 133MHz. Libata has a hook
 > >  >    pdc2027x_post_set_mode() to set the values back by software.
 > >  > 
 > >  > 3. ATAPI DMA is supported (please see pdc2027x_check_atapi_dma()).
 > >  >    Maybe we also need to add this to the IDE version.
 > 
 > > Do you know how large the difference is between the 20267 (old driver)
 > > and the 20269 (new driver) in the areas touched by these patches?
 > 
 >     Immense. They belong to the different families, register compatibe only in 
 > the standard PCI/BM IDE regisrer set -- hence was the driver split.
 > 
 > > Long ago I tried a 20267 PCI card in my PowerMac, and it had the same
 > > issues that the 20269 card had. So I'm interested in porting the
 > > calibration/timing fixes to pdc202xx_old.c.
 > 
 >     They don't apply to this driver at all.  The "older" chip family didn't 
 > have the PLL to calibrate.  It must be some different issue.

OK, in that case let's forget about the 20267. It's not _that_ important :-)

  reply	other threads:[~2006-08-09 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 23:58 Mikael Pettersson
2006-07-18 18:07 ` Sergei Shtylyov
2006-07-27  4:31   ` Albert Lee
2006-07-27 16:35     ` Sergei Shtylyov
2006-08-09 15:59     ` Mikael Pettersson
2006-08-09 16:05       ` Sergei Shtylyov
2006-08-09 16:15         ` Mikael Pettersson [this message]
2006-07-19  0:29 Mikael Pettersson
2006-07-25 16:02 ` 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=17626.2593.367175.896926@alkaid.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=alan@redhat.com \
    --cc=albertl@mail.com \
    --cc=dwm@enoyolf.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=sshtylyov@ru.mvista.com \
    --cc=uchang@tw.ibm.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

all inboxes | Powered by JetHome®