All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dmalek@jlc.net>
To: Cort Dougan <cort@ppc.kernel.org>
Cc: Neil Blackwood <nb@terrafix.co.uk>,
	sorin@nitechinc.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: IDE on MBX board
Date: Mon, 22 Nov 1999 18:59:57 -0500	[thread overview]
Message-ID: <3839D8FD.2D6EE79D@jlc.net> (raw)
In-Reply-To: 19991122115254.A29168@chimaera.ppc.kernel.org


Cort Dougan wrote:


> .........  One of the big problems was tracking down
> the interrupt routing for IDE on the MBX.  If you check to see if you're
> getting any interrupts at all on the 8259 that may give you a good place to
> start.
> 
> I don't have an IDE drive for my MBX anymore but would like to have it
> working again.  Let me know if you want to work together on it.

I have a couple of projects over the next month or so (if the hardware
arrives :-) that include some kind of IDE disk interface.  They are not
PCI/ISA devices, rather unique hardware interfaces to the bus. I
also have the 8240/Sandpoint to finish, which currently has a similar
interrupt routing problem you mention above (integrated interrupt
controller with external 8259).  I also want the pcmcia-cs running
on the 8xx, which means we have to make IDE work there (and I think it
is still broken on the PowerBooks :-).

It appears there are enough of us to get it working, so let's just
keep in touch and post the progress.


	-- Dan

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

  reply	other threads:[~1999-11-22 23:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-19 14:31 IDE on MBX board Sorin Balea
1999-11-22 11:19 ` Neil Blackwood
1999-11-22 16:56   ` Dan Malek
1999-11-22 18:52     ` Cort Dougan
1999-11-22 23:59       ` Dan Malek [this message]
1999-11-22 16:46 ` Dan Malek
1999-11-22 16:22   ` Sorin Balea
1999-11-22 19:54     ` Dan Malek

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=3839D8FD.2D6EE79D@jlc.net \
    --to=dmalek@jlc.net \
    --cc=cort@ppc.kernel.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=nb@terrafix.co.uk \
    --cc=sorin@nitechinc.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.