linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Joseph Chan <JosephChan@via.com.tw>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	HaraldWelte@viatech.com
Subject: [RFC PATCH 0/2] sata_via: fix TF access and add 8251 support
Date: Thu, 02 Oct 2008 10:53:09 +0900	[thread overview]
Message-ID: <48E42985.60400@kernel.org> (raw)

Hello, Joseph and Harald.

I'm gonna send two patches as reply to this message.  Can you please
review them?  Both are separated out from Joseph's original patch.

  http://thread.gmane.org/gmane.linux.kernel.commits.mm/40640

The former one (fix TF load) is rather straight-forward and it seems
to work on my vt6421's but I couldn't test 8251 support as I don't
have any.  I thought the controller you sent me was 8251 but it was
6421, right?  I think I asked for 6421 not knowing what I wanted was
8251.  So, it would be great if you can test whether the 8251 support
works.  Please post the kernel log whether it succeeds or not.

For the time being, I skipped support for 0581 and 5324 as they were
not on the PCI device ID list of the original patch.  Do they have the
same configuration?  Or are they SATA/PATA mixed?

The patches are on top of the upstream branch of Jeff's libata-dev
tree.

 git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
 http://www.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git

Thanks.

-- 
tejun

             reply	other threads:[~2008-10-02  1:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02  1:53 Tejun Heo [this message]
2008-10-02  1:54 ` [RFC PATCH 1/2] sata_via: load DEVICE register when CTL changes Tejun Heo
2008-10-02  1:54 ` [RFC PATCH 2/2] sata_via: fix support for 5287 Tejun Heo
2008-10-06  9:56 ` [RFC PATCH 0/2] sata_via: fix TF access and add 8251 support Harald Welte

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=48E42985.60400@kernel.org \
    --to=tj@kernel.org \
    --cc=HaraldWelte@viatech.com \
    --cc=JosephChan@via.com.tw \
    --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).