Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Helge Deller <deller@gmx.de>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] 32bit parisc kernel 2.6.1 and pcmcia
Date: 19 Jan 2004 20:16:30 -0500	[thread overview]
Message-ID: <1074561391.2081.17.camel@mulgrave> (raw)
In-Reply-To: <200401192248.29566.deller@gmx.de>

On Mon, 2004-01-19 at 16:48, Helge Deller wrote:
> Wouldn't it be possible to write a wrapper, which simulated the
> ISA IRQs 0-15 and routes them to dino instead ?
> Isn't this similiar like the hack we have for the EISA driver ?
> And maybe we are lucky and no PA-machine has both, EISA and PCMCIA.
> Would this be possible ?

OK...Just to confirm what you're getting yourself into:

The yenta socket is a deep black art.  It also covers a multitude of
slightly different standards (from different manufacturers).  I learned
enough of the sourcery to say the required incantations for my
particular needs (which were a B180 with a PCI<->cardbus yenta socket
that came free with my zoom wireless card).

In order to get my setup to work, I also had to replumb virtually the
whole of the dino PCI system (I needed this because the B180 firmware
barfed at the PCMCIA socket and simply disabled it).

The point, I'm afraid, is that although I got it work for me, I'll bet
not much of the magic is transferrable, so you may also find yourself
ploughing through the yenta specs...

If this hasn't deterred you, then read on intrepid adventurer.

One of the things you seem to have from the error messages is IRQ
misrouting.  Could you boot up (or stop PCMCIA, remove all the modules,
including the core and restart) with a card in the socket?  The socket
status should tell us which one, and the IRQ line is given by lspci. 
Since the chip is both PCI device functions, it's not impossible to have
the IRQ routings messed up.

James

      parent reply	other threads:[~2004-01-20  1:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-18 19:59 [parisc-linux] 32bit parisc kernel 2.6.1 and pcmcia Helge Deller
2004-01-18 23:44 ` James Bottomley
2004-01-19  9:07   ` Helge Deller
2004-01-19 14:38     ` James Bottomley
2004-01-19  5:59 ` Grant Grundler
2004-01-19  9:03   ` Helge Deller
2004-01-19 14:35 ` James Bottomley
2004-01-19 21:48   ` Helge Deller
2004-01-20  0:50     ` Grant Grundler
2004-01-20  1:16     ` James Bottomley [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=1074561391.2081.17.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=deller@gmx.de \
    --cc=parisc-linux@lists.parisc-linux.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