From: Paul Mackerras <paulus@samba.org>
To: msokolov@ivan.Harhan.ORG (Michael Sokolov)
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: VT82C686B IDE and Linux/PPC woes
Date: Tue, 27 Nov 2001 13:50:32 +1100 (EST) [thread overview]
Message-ID: <15362.65400.567302.796449@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <0111262205.AA22280@ivan.Harhan.ORG>
Michael Sokolov writes:
> Yet when I boot Linux/PPC, it sees the IDE ports, but doesn't see the drive
> attached to the IDE0 port (see the session log below). My port in
> arch/ppc/platforms does absolutely nothing IDE-related, in .config I have IDE
> and VT82C686B support enabled. Is there something that my Linux/PPC port has to
> do explicitly with IDE in order for it to work?
Hmmm, there shouldn't be any problem. You do have CONFIG_BLK_DEV_IDEPCI
enabled I assume? Your k2_ide_init_hwif_ports looks OK to me. I
would scatter some printks through drivers/ide/ide-pci.c to try to get
an idea what it is doing and where it is going wrong.
BTW, I can't see any reason why we still need to have
ide_init_hwif_ports be platform-specific. It is only used for
PC-style IDE interfaces and for PCI IDE interfaces. For other types
of interface we should be adding a probe call in ide.c rather than
trying to do it with ide_default_io_base and ide_init_hwif_ports.
Not that this applies to the k2.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-27 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 22:05 VT82C686B IDE and Linux/PPC woes Michael Sokolov
2001-11-26 23:35 ` Adrian Cox
2001-11-27 2:50 ` Paul Mackerras [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 18:27 Michael Sokolov
2001-11-27 19:01 ` Adrian Cox
2001-11-27 17:10 Michael Sokolov
2001-11-27 17:26 ` Adrian Cox
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=15362.65400.567302.796449@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--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).