From: "Mark A. Greer" <mgreer@mvista.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Sarnath Kannan <sparc64@rediffmail.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: IDE in Mode 1 (Sandpoint) how ?
Date: Mon, 12 Nov 2001 12:55:13 -0700 [thread overview]
Message-ID: <3BF02921.2C95A660@mvista.com> (raw)
In-Reply-To: 3BEFF427.4000309@embeddededge.com
Dan Malek wrote:
> Sarnath Kannan wrote:
>
> > hi all,
> > The Sandpoint user's manual says that WinBond's IDE controller is disabled in mode 1 (s3-down, s4-up), but MontaVista's kernel works in mode 1 with IDE support!
> > How is this possible ?
Because the documentation is misleading...
> The up/down comment is relative to the installation of the board in the chassis.
> Mine are actually the other way around. I'm not even sure if on/off nomenclature
> would work.
Sarnath, Dan is completely correct, it is relative so you need to first *carefully read* the comments in sandpoint_setup.c that describe the switch setting,
*understand them*, and then *follow them*. Especially the part where it says:
" * 'down' is in the direction from the PCI slots towards the PPMC slot;
* 'up' is in the direction from the PPMC slot towards the PCI slots.
* Be careful, the way the sandpoint board is installed in XT chasses will
* make the directions reversed."
> Just keep in mind the troubles are local to your configuration, as this software
> operates fine on a properly configured board. Just move switches until it works,
> then leave them alone :-).
ditto
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-12 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 12:46 IDE in Mode 1 (Sandpoint) how ? Sarnath Kannan
2001-11-12 16:09 ` Dan Malek
2001-11-12 19:55 ` Mark A. Greer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 4:07 Sarnath Kannan
2001-11-13 5:25 ` Dan Malek
2001-11-13 8:17 Sarnath Kannan
2001-11-13 16:18 ` Dan Malek
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=3BF02921.2C95A660@mvista.com \
--to=mgreer@mvista.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sparc64@rediffmail.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;
as well as URLs for NNTP newsgroup(s).