From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Karl Auerbach <karl@iwl.com>,
linux-ide@vger.kernel.org, karl@cavebear.com
Subject: Re: Some IDE issues with 2.6.28 on PC-Engines ALIX2
Date: Mon, 05 Jan 2009 20:47:22 +0300 [thread overview]
Message-ID: <496247AA.1040809@ru.mvista.com> (raw)
In-Reply-To: <20090105133340.050858bb@lxorguk.ukuu.org.uk>
Hello.
Alan Cox wrote:
>>>The IDE interface of the Geode CS5536 companion chip is a completely
>>>different beast. It's a more or less standard AMD 8111 PCI IDE device
>>>with slightly different timings.
>> I'm not sure I uderstand the passage about "slightly different
>>timings"...
> The timing values used are different to those on the AMD 8111 even though
> the interface is similar.
What do you mean by timing values anyway, clock counts or the register
encoding itself?
>> It's stange that the driver is using CPI config. space by default
>>which not even documented in the datasheet. I guess the MSR accesses are
> The PCI configuration is the portable way to drive it.
Portable to what? As you have yorself noted below, this is Geode -- and I
highly doubt that CS5536 will be used for anything else.
>>also somewhat faster because one doesn't have to access the address/data
>>register pair at ports 0xcf8/0xcfc...
> This is a Geode.
I know. :-)
I have hacked on older Geode GX2 for some time back in 2004 (although not
on something related to PCI); my "toy" board has RIP just recently.)
> What makes you think there is even a PCI bus
I sure know that it's not PCI (IIUC, it's the common tendency in the x86
north-to-south-bridge busses has been emulating the PCI config. space with
less and less PCI compatible "physical layer"). That does mean emulating PCI
config. space mechanism #1 and Geode's not an exception here, see:
http://www.amd.com/files/connectivitysolutions/geode/geode_gx/32663C_lx_gx_pciconfig.pdf
> or that the 8111 interface isn't entirely a software construct.
If that's the case (looks like so), it makes using it even appealing...
> Geode PCI hardware is mostly smoke and mirrors ;)
When it comes to their internal controllers, yes (though e.g. their OHCI
seem to have the real PCI config. space).
> Alan
WBR, Sergei
next prev parent reply other threads:[~2009-01-05 17:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 0:37 Some IDE issues with 2.6.28 on PC-Engines ALIX2 Karl Auerbach
2009-01-05 3:01 ` Martin K. Petersen
2009-01-05 12:44 ` Sergei Shtylyov
2009-01-05 13:33 ` Alan Cox
2009-01-05 17:47 ` Sergei Shtylyov [this message]
2009-01-05 18:04 ` Alan Cox
2009-01-05 18:44 ` Martin K. Petersen
2009-01-05 11:36 ` Alan Cox
2009-01-05 23:23 ` Karl Auerbach
2009-01-05 23:27 ` Alan Cox
2009-01-06 12:58 ` Sergei Shtylyov
2009-01-06 19:21 ` Alan Cox
2009-01-06 19:54 ` Bartlomiej Zolnierkiewicz
2009-01-05 12:08 ` Sergei Shtylyov
2009-01-05 16:36 ` Bartlomiej Zolnierkiewicz
2009-01-05 16:52 ` Alan Cox
2009-01-05 17:15 ` Bartlomiej Zolnierkiewicz
2009-01-05 17:19 ` Alan Cox
2009-01-05 17:38 ` Bartlomiej Zolnierkiewicz
2009-01-05 18:00 ` Alan Cox
2009-01-05 18:10 ` Bartlomiej Zolnierkiewicz
2009-01-05 22:41 ` Sergei Shtylyov
2009-01-11 17:47 ` Bartlomiej Zolnierkiewicz
2009-01-31 21:03 ` Sergei Shtylyov
2009-02-01 16:16 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2009-01-31 11:25 Christoph .J Thompson
2009-01-31 12:53 ` Martin K. Petersen
2009-01-31 14:15 ` Sergei Shtylyov
2009-01-31 14:58 ` Martin K. Petersen
2009-01-31 14:42 ` Sergei Shtylyov
2009-01-31 16:27 ` Christoph .J Thompson
2009-01-31 16:35 ` Mark Lord
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=496247AA.1040809@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=karl@cavebear.com \
--cc=karl@iwl.com \
--cc=linux-ide@vger.kernel.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.