Subject: Re: TI TravelMate 5000 pcmcia problems?
To: Charlie Allom <charlie@rubberduck.com>
From: Greywolf <greywolf@starwolf.com>
List: current-users
Date: 09/04/2002 18:22:02
On Thu, 5 Sep 2002, Charlie Allom wrote:

# Date: Thu, 5 Sep 2002 11:03:27 +1000
# From: Charlie Allom <charlie@rubberduck.com>
# To: Martin Husemann <martin@duskware.de>
# Cc: current-users@netbsd.org
# Subject: Re: TI TravelMate 5000 pcmcia problems?
#
# On Wed, Sep 04, 2002 at 02:13:56PM +0200, Martin Husemann wrote:
# > On Wed, Sep 04, 2002 at 09:38:57PM +1000, Charlie Allom wrote:
# >
# > > How do I go about setting the IRQ? options PCIC_ISA_INTR_ALLOC_MASK=?
# >
# > Duh, just noticed my (working) system does not print the irq either:
# >
# > pcic0 at isa0 port 0x3e0-0x3e1 iomem 0xd0000-0xdffff irq
# > pcic0: controller 0 (Intel 82365SL Revision 1) has socket A only
# > pcic0: controller 1 (Intel 82365SL Revision 1) has no sockets
# > pcmcia0 at pcic0 controller 0 socket 0
# >
# > The interesting part comes later (after interrupts have been enabled):
# >
# > pcic0: controller 0 detecting irqs with mask 0xdeb8:..7..9..14
# > pcic0: using irq 7 for socket events
#
# dmesg:
#
# pcic0: using irq 3 for socket events
#
# I have this set in my kernel config:
#
# options         PCIC_ISA_ALLOC_IOBASE=0x300
# options         PCIC_ISA_ALLOC_IOSIZE=0x0ff
# options         PCIC_ISA_INTR_ALLOC_MASK=0x0008
#
# after this from options(4)
#
#      options PCIC_ISA_INTR_ALLOC_MASK=mask
#      Controls the allowable interrupts that may be used for PCMCIA
# devices.
#      This mask is a logical-or of power-of-2s of allowable interrupts:
#
#         IRQ Val      IRQ Val      IRQ Val       IRQ Val
#          0  0x0001    4  0x0010    8  0x0100    12  0x1000
#          1  0x0002    5  0x0020    9  0x0200    13  0x2000
#          2  0x0004    6  0x0040   10  0x0400    14  0x4000
#          3  0x0008    7  0x0080   11  0x0800    15  0x8000
#
# Am I doing anything wrong? Could I be righter? :)
#
#   C.

Yeled,

You might want to figure out what interrupts you have available and let
the device choose from those (the appropriate mask from above is left as
an exercise for the reader);  apparently you are explicitly telling the
driver that you ONLY have IRQ 3 available -- is this really what you want
to do?

[To answer your question, yes, that's the effect that the mask you've
specified is having -- forcing it to IRQ 3.]

				--*greywolf;
--
NetBSD: It's not Windows.