From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Martin K. Petersen" <mkp@mkp.net>
Cc: Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, info-linux@geode.amd.com
Subject: Re: pata_cs5536: ATA driver for Geode companion chip
Date: Wed, 3 Oct 2007 17:30:12 -0600 [thread overview]
Message-ID: <20071003233012.GA8721@cosmic.amd.com> (raw)
Hi Martin - make sure you CC me on responses, I'm not on linux-ide.
> 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.
There are multiple ways to do it, simply because of the way the architecture
is designed underneath. Thats why we enforce the policy
of using the PCI mechanism when ever we can to encourage everybody on the
same page.
> 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.
No - I think if we're going to have the different timings, they should
be in their own driver, not bothering the other users of this IP.
> 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.
Thats a bug, pure and simple. If the PCI space is there, but the IDE
registers are not - then you are deep into breakage mode, and you need
to yell very loud and very long at your BIOS vendor.
In the standard AMD VSA, writeos to PCI space 0x48 (DTC), 0x49 (CAST) and
0x50 (ETC) should work - and the change should be immediately reflected
in the MSR. You can see for yourself, the code is open:
http://dev.laptop.org/git?p=geode-vsa;a=blob;f=sysmgr/pci_wr.c;h=9a984998ba3b8ed06358a85faf16a6ddebdad4a9;hb=HEAD#l359
Not all BIOS vendors follow the AMD model, but most do.
> PS. So what's the story wrt. a PRD length of 0?
Alan is right, the NSC/Cyrix block had issues. Thats why when we started
on the 5536, we searched around in AMD's attic, and found
the 8111 IDE block under an pile of old clothes and Life magazines.
We dusted it off and stuck it in. So this fundamentally different
silicon then before.
I believe that the datasheet is correct - at least, there aren't any
errata, and we've been pretending to be a AMD74xx for quite a while now
with no ill effects in this regard.
Jordan
--
Jordan Crouse
Systems Software Development Engineer
Advanced Micro Devices, Inc.
next reply other threads:[~2007-10-03 23:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 23:30 Jordan Crouse [this message]
2007-10-04 3:29 ` pata_cs5536: ATA driver for Geode companion chip 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
2007-10-05 6:06 ` [PATCH] pata_cs5536: ATA driver for Geode companion chip (PCI) Martin K. Petersen
2007-10-05 6:07 ` [PATCH] pata_cs5536: ATA driver for Geode companion chip (MSR) Martin K. Petersen
2007-10-05 12:01 ` Alan Cox
2007-10-05 14:53 ` Jordan Crouse
2007-10-05 19:00 ` [PATCH] " Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2007-10-03 17:28 [PATCH 1/1] pata_cs5536: ATA driver for Geode companion chip Martin K. Petersen
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
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
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=20071003233012.GA8721@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=info-linux@geode.amd.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mkp@mkp.net \
/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).