linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: guinan@bluebutton.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MBX IDE
Date: Thu, 29 Jun 2000 04:45:27 -0400	[thread overview]
Message-ID: <395B0CA7.3B3AC0E5@netx4.com> (raw)
In-Reply-To: Pine.LNX.4.21.0006290329430.23317-100000@gemini.home.net


Jamie Guinan wrote:

> m8xx_setup.c doesn't seem to want both IDE and PCMCIA ATA devices
> to exist at the same time, though.  Not sure what to do about that,


It's an interrupt routing issue.  In fact, all of the support
for SouthBridge/8259 controller parts on an 8xx is an interrupt
routing issue.  Mapping the internal interrupts from something
like the PCMCIA into the same space as the PCI/ISA has never
worked in the 8xx port.  You basically get to configure an
"8xx PC" or an "8xx embedded".  Cort and I are constantly working
on some better interrupt mapping scheme, some of it "sticks" in
the kernel sources.  The entire Linux kernel is either "PC" or
not.

I don't know of any production boards that support PCI with ISA
on an 8xx.  You can program the UPM to provide ISA bus timing,
or for a few pennies put a programmable device on the 8xx bus
if you want an IDE device.

> .....  If I can hack
> them to both work at the same time for my own purposes, I'll
> be happy.

You can.....It just won't run on anything else when you are done.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-06-29  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-28 12:22 MBX IDE Jamie Guinan
2000-06-28 15:46 ` Zirong Wang
2000-06-29  7:56 ` Jamie Guinan
2000-06-29  8:45   ` Dan Malek [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=395B0CA7.3B3AC0E5@netx4.com \
    --to=dan@netx4.com \
    --cc=guinan@bluebutton.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).