From: "Mark A. Greer" <mgreer@mvista.com>
To: "ZHANG,HAI-TAO (Non-A-China,ex1)" <hai-tao_zhang@non.agilent.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: IDE on Sandpoint
Date: Tue, 05 Sep 2000 15:33:21 -0700 [thread overview]
Message-ID: <39B574B1.D7AD139A@mvista.com> (raw)
In-Reply-To: 2F67A63DFFB1D31185D90090278CBB2D014ECAAE@apmail6.chn.agilent.com
Yes, I had to make some minor changes to the driver to get ide to work (plus
add support to sandpoint_setup.c).
Go to ftp://www.mvista.com/pub/Area51/sandpoint-8240/ and get
sandpoint.linux.tar.gz. This is a tarball of kernel source that has IDE
working (at least on an 8240 and a 755/107). I just put it there so let me
know if you have any problems ftp'ing it or its corrupted or something.
This kernel routes ide interrupts to the standard ISA/8259 IRQ's, namely 14 &
15.
Mark
> Hi,
>
> I have tried to boot Linux kernel on Sandpoint 603e using the nfsroot. But I
> cannot make the IDE working under Mode 1.
>
> There are some comments from MontaVista CDK1.2:
> "5) If you want to try IDE, you must route the IDE interrupts through the
> i8259; they are not wired to PCI slots 1 & 2 as the Sandpoint manual
> indicates."
>
> In the Winbond 83c553 manual, there are some registers that can route the
> IDE IRQ into 8259 (IRQ14). I have tried to set them but it does not work, do
> I need to modify the hardware? or someone has the successful experience on
> IDE disk who can help me?
>
> Thanks a lot,
> Haitao Zhang,
>
--
Mark A. Greer (mgreer@mvista.com; 480-517-0287)
MontaVista Software, Inc.
2141 E. Broadway Road, Suite 108
Tempe, AZ 85282
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-05 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 3:33 IDE on Sandpoint ZHANG,HAI-TAO (Non-A-China,ex1)
2000-09-05 22:33 ` Mark A. Greer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-06 9:58 ZHANG,HAI-TAO (Non-A-China,ex1)
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=39B574B1.D7AD139A@mvista.com \
--to=mgreer@mvista.com \
--cc=hai-tao_zhang@non.agilent.com \
--cc=linuxppc-embedded@lists.linuxppc.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).