linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Uwe Steinmann <steinm@majestix.fernuni-hagen.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Uwe Steinmann <steinm@majestix.fernuni-hagen.de>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Again PCMCIA problems
Date: Tue, 18 Dec 2001 10:24:13 +0100	[thread overview]
Message-ID: <20011218102413.A14636@gehtnix.fernuni-hagen.de> (raw)
In-Reply-To: <15390.52568.449162.783080@argo.ozlabs.ibm.com>; from paulus@samba.org on Tue, Dec 18, 2001 at 04:00:08PM +1100


On Tue, Dec 18, 2001 at 04:00:08PM +1100, Paul Mackerras wrote:
> Uwe Steinmann writes:
>
> > Thanks for the help so far, I got finally a bit further, and it looks
> > very promissing but ran into another problem. For some reason the request for
> > irg 58 failled.
> >
> > Dec 17 16:46:50 pb cardmgr[10624]: re-loading config file
> > Dec 17 16:46:52 pb cardmgr[10624]: initializing socket 0
> > Dec 17 16:46:52 pb cardmgr[10624]: socket 0: AVM ISDN-Controller A1
> > Dec 17 16:46:53 pb cardmgr[10624]: executing: 'modprobe isdn'
> > Dec 17 16:46:53 pb cardmgr[10624]: executing: 'modprobe hisax id=hisax1 type=26 protocol=2'
> > Dec 17 16:46:53 pb kernel: avma1_cs: testing i/o 0x140-0x149
> > Dec 17 16:46:53 pb kernel: avma1_cs: checking at i/o 0x140, irq 58
> > Dec 17 16:46:53 pb kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
> > Dec 17 16:46:53 pb kernel: HiSax: AVM A1 PCMCIA driver Rev. 1.1.4.1
> > Dec 17 16:46:53 pb kernel: AVM A1 PCMCIA: io 0x140 irq 58 model 1 version 2
> > Dec 17 16:46:53 pb kernel: AVM A1 PCMCIA: ISAC version (0): 2086/2186 V1.1
> > Dec 17 16:46:53 pb kernel: AVM A1 PCMCIA: HSCX version A: V2.1  B: V2.1
> > Dec 17 16:46:53 pb kernel: AVM A1 (PCMCIA): IRQ 58 count 0
> > Dec 17 16:46:53 pb kernel: HiSax: couldn't get interrupt 58
>
> On powerbooks, the card functional interrupt is shared with the card
> controller interrupt.  That is, your HiSax card will use the same
> interrupt for its operations as the TI cardbus controller.  Thus, if
> the HiSax driver doesn't include SA_SHIRQ in the flags value to the
> request_irq call, the request_irq will fail.  I would say that is what
> you are seeing.
You were quite right. There is a define in hisax.h where I4L_IRQ_FLAGS is
set to 0. If I change this to SA_SHIRQ it works! At least the card can be
configured. I'll check if I can get an internet connection over ISDN as
soon as I'm back home.

I'll send a note to the maintainer of the hisax driver.

Thanks for the help.

  Uwe
--
  MMK GmbH, Hagen
  Uwe.Steinmann@mmk-hagen.de
  Tel: +2331 987 4528    Fax: +2331 987 375

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

      reply	other threads:[~2001-12-18  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20011212140119.A12086@gehtnix.fernuni-hagen.de>
2001-12-12 14:44 ` Again PCMCIA problems Benjamin Herrenschmidt
2001-12-17 18:16   ` Uwe Steinmann
2001-12-18  5:00     ` Paul Mackerras
2001-12-18  9:24       ` Uwe Steinmann [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=20011218102413.A14636@gehtnix.fernuni-hagen.de \
    --to=steinm@majestix.fernuni-hagen.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.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).