From: Adrian Cox <adrian@humboldt.co.uk>
To: Michael Sokolov <msokolov@ivan.Harhan.ORG>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: VT82C686B IDE and Linux/PPC woes
Date: Tue, 27 Nov 2001 19:01:00 +0000 [thread overview]
Message-ID: <3C03E2EC.5020102@humboldt.co.uk> (raw)
In-Reply-To: 0111271827.AA24645@ivan.Harhan.ORG
Michael Sokolov wrote:
> Adrian Cox <adrian@humboldt.co.uk> wrote:
> P.S. When I took the pciauto_bus_scan() calls out, it saw the drive, but hung
> on the partition check. Disabling the VIA82CXXX support .config and leaving
> only the generic PCI IDE support made it really work. I guess the VIA82CXXX
> fast modes code still has issues to be worked out. Maybe it's because it
> assumes there is a BIOS and in my case there isn't one. (My minimalist firmware
> does not touch any VT82C686B IDE stuff at all, and yet if I want I can pull the
> IDE register addresses out of the BARs and see the drive there using ancient
> WD100x code.)
The driver assumes that the BIOS has correctly probed for cable types. I
believe this is because the board designer gets to choose which GPIO on
the 686B they wire the cable detection to. You'll need to check the
layout, and study that section of the 686B manual.
--
Adrian Cox http://www.humboldt.co.uk/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-27 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 18:27 VT82C686B IDE and Linux/PPC woes Michael Sokolov
2001-11-27 19:01 ` Adrian Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 17:10 Michael Sokolov
2001-11-27 17:26 ` Adrian Cox
2001-11-26 22:05 Michael Sokolov
2001-11-26 23:35 ` Adrian Cox
2001-11-27 2:50 ` Paul Mackerras
2001-11-26 21:26 Michael Sokolov
2001-11-26 22:04 ` mod+linuxppc-embedded
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=3C03E2EC.5020102@humboldt.co.uk \
--to=adrian@humboldt.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=msokolov@ivan.Harhan.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).