From: Daniel Jacobowitz <drow@false.org>
To: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PCI resource assignment
Date: Mon, 5 Jun 2000 12:59:35 -0700 [thread overview]
Message-ID: <20000605125935.A21551@quaketop.them.org> (raw)
In-Reply-To: <Pine.LNX.4.05.10006050927350.5397-100000@callisto.of.borg>; from geert@linux-m68k.org on Mon, Jun 05, 2000 at 09:42:02AM +0200
On Mon, Jun 05, 2000 at 09:42:02AM +0200, Geert Uytterhoeven wrote:
> - I don't know what to do with the code marked with
>
> Don't touch IDE controllers and I/O ports of video cards!
>
> Perhaps we do need to touch IDE controllers on PPC? I don't have IDE
> devices connected to the IDE interface in my LongTrail, so I don't know.
> AFAIK the IDE interface does work without fiddling with the PCI resources
> on other LongTrails, but that could be caused by the different OF in those
> boxes (that different OF does assign other missing resources, unlike mine).
My experience is that we need to touch IDE cards without Open Firmware
ROM. I currently have a card that needs this; I have a hideous local
hack in my kernel to enable it.
>
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-05 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-05 7:42 PCI resource assignment Geert Uytterhoeven
2000-06-05 19:59 ` Daniel Jacobowitz [this message]
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=20000605125935.A21551@quaketop.them.org \
--to=drow@false.org \
--cc=linuxppc-dev@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).