Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Aug 2000 10:12:45 +0100
From:      Brian Candler <B.Candler@pobox.com>
To:        Warner Losh <imp@village.org>
Cc:        freebsd-mobile@FreeBSD.ORG, shigeru@iij.ad.jp
Subject:   Re: Ricoh RL5C475 PCI-PCMCIA adaptor and interrupts
Message-ID:  <20000807101245.C13919@linnet.org>
In-Reply-To: <200008062052.OAA26562@harmony.village.org>; from imp@village.org on Sun, Aug 06, 2000 at 02:52:12PM -0600
References:  <20000806204051.A805@linnet.org> <200008062052.OAA26562@harmony.village.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 06, 2000 at 02:52:12PM -0600, Warner Losh wrote:
> : (2) Worse, what if there are other boards based on the Ricoh RL5C475 which
> : need the bit to be set? It would be hard or impossible to determine this
> : from the PCI ID, so you'd have to make it a user-settable flag :-(
> 
> Yes.  That's going to make things tough.  In the future, we'll not
> kick these cards into legacy '365 emulation mode, so a temp hack like
> this is OK for now.  However, I don't think this hack works :-(.
> 
> I think you'll have to check to see if an interrupt is allocated to
> the card and do this trick if one isn't.  My laptop has a 475 in it
> and it works 100% of the time w/o this bit set, so something better
> must be done.  I'm fairly certain that enabling this code on my laptop 
> would make it fail 100% of the time (since I recall having to add it
> to make it work there).

We may have a clash of terminology; this bit is actually set to 1 in the
existing (unmodified) code, but I had to clear it for my board.

So, in your laptop, does the 475 appear as a PCI device? But then they have
wired the ISA interrupt pins directly to the ISA interrupt controller?
Yeuch.

In that case, we would need a clean way to distinguish between:
(1) a 475 which is actually sitting on a PCI card
(2) a 475 which is directly connected

and as you say, short of probing interrupts, that's difficult to do. BTW, a
note in the Linux pcmcia-cs-3.1.19 code says that interrupt probing for
Ricoh chips seems to be unreliable, and it is disabled (except for checking
for a stuck-on interrupt)

> What does dmesg say for you when you boot?  I'm interested only in the 
> pcic-pci* line(s).

I'll dig this out when I'm next in front of the machine. It said something
along the lines of Ricoh 5C475 at slot 8.0 on irq 11.

Cheers,

Brian.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000807101245.C13919>