From: "Martin K. Petersen" <mkp@mkp.net>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-ide@vger.kernel.org
Subject: Re: pata_cs5536: ATA driver for Geode companion chip
Date: Wed, 03 Oct 2007 18:32:01 -0400 [thread overview]
Message-ID: <yq1tzp7de3i.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20071003211856.GB2916@cosmic.amd.com> (Jordan Crouse's message of "Wed\, 3 Oct 2007 15\:18\:56 -0600")
>>>>> "Jordan" == Jordan Crouse <jordan.crouse@amd.com> writes:
Jordan> That should work on any AMD VSA derivatives. There are some
Jordan> who may have rolled their own, and they don't support the same
Jordan> virtual registers. in that case, you can check if SMIs are
Jordan> enabled - that would be a reasonable indication that there is
Jordan> something VSAish out there.
I'll try this later and see what comes up. But I'm not sure I see the
advantage of having two ways to configure the 5536.
I was simply interested in getting things configured correctly. I
agree that ideally all platforms would simply Do The Right Thing.
However, I took the pragmatic/safe approach and used the MSRs to
configure the beast. The only reason I even tried is that this is a
setup issue exclusively. Had the actual I/O interface been hiding in
a similar fashion I wouldn't have bothered.
Early on I also had some funny results with PIO so another reason I
wrote pata_cs5536 was to use the values specified in the databook. It
seemed cleaner to have a tiny separate driver than to wedge another
set of timings into pata_amd.c.
I agree that it would be silly to have two drivers if there was actual
functionality lurking in them. But as it stands most of the pata_*
drivers are simply configuration templates and nothing more.
Anyway. That's my personal take on it. If there's a general
consensus that the timings should be in pata_amd.c then so be it.
Jordan> But you bring up another point - I'm not sure that Martin
Jordan> _doesn't_ have VSA. He is initializing this as a PCI driver,
Jordan> so he has something out there listening to CF8/CFC, or he's
Jordan> emulating the OLPC spoof mechanism [1].
The board I'm using has a BIOS which exposes the IDE registers in PCI
space but doesn't appear to listen when they are written to. I'm
hoping that will get fixed eventually.
PS. So what's the story wrt. a PRD length of 0?
--
Martin K. Petersen http://mkp.net/
next prev parent reply other threads:[~2007-10-03 22:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 17:28 [PATCH 1/1] pata_cs5536: ATA driver for Geode companion chip Martin K. Petersen
2007-10-03 18:22 ` Alan Cox
2007-10-03 18:20 ` Jeff Garzik
2007-10-03 18:45 ` Martin K. Petersen
2007-10-03 18:51 ` Alan Cox
2007-10-03 20:31 ` Jordan Crouse
2007-10-03 20:59 ` Alan Cox
2007-10-03 21:18 ` Jordan Crouse
2007-10-03 22:32 ` Martin K. Petersen [this message]
2007-10-03 22:56 ` Jeff Garzik
2007-10-10 1:25 ` [PATCH 1/1] " Jeff Garzik
2007-10-10 4:33 ` Martin K. Petersen
2007-10-10 15:20 ` Jordan Crouse
2007-10-10 17:39 ` Andrew Paprocki
2007-10-11 7:22 ` Andrew Paprocki
-- strict thread matches above, loose matches on Subject: below --
2007-10-03 23:30 Jordan Crouse
2007-10-04 3:29 ` Martin K. Petersen
2007-10-04 12:04 ` Alan Cox
2007-10-04 15:58 ` Alan Cox
2007-10-04 16:08 ` Jordan Crouse
2007-10-04 16:22 ` Alan Cox
2007-10-04 17:00 ` Martin K. Petersen
2007-10-05 6:05 ` Martin K. Petersen
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=yq1tzp7de3i.fsf@sermon.lab.mkp.net \
--to=mkp@mkp.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jordan.crouse@amd.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).