From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] 3c509b troubles
Date: Sat, 30 Aug 2008 07:05:30 +0200 [thread overview]
Message-ID: <dab04424b8848545eb53dfb563094703@proxima.alt.za> (raw)
In-Reply-To: <3df301650808291825m2e9db4a0hd0f810ff60201e25@mail.gmail.com>
> heh. geez am i dopey. the problem was my misunderstanding of what the
> irq=xx parts in plan9.ini do. bios decides the irq, plan9.ini tells
> the kernel what the bios decided. that's my isa card mantra from now
> on
I was going to suggest you base your configuration on what OpenBSD
determines. It I remember right (I have a few 3Com cards I treasure)
they all allowed an autoconfiguration that predates PnP but resembles
it somehow: identify the autoconfiguration port and wiggle it to tell
the card where to enable IRQ, I/O and possibly DMA.
Plan 9 may have had an issue with the configuration port. ISA has a
big issue with shared IRQs: IBM engineered the IRQs to be
level-triggered and active low TTLs, so an inactive card would mask
any other card reporting an interrupt on the same line. I was told
some of these decisions (the choice of 8250s instead of 8251s for
serial communication, for example) were intentional.
OK, there I go showing off :-) Just in case people think I'm still the
fourteen year old weenie in the "face" archive and get shocked when I
pitch up in Volos :-)
++L
prev parent reply other threads:[~2008-08-30 5:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 17:40 michael block
2008-08-29 18:06 ` erik quanstrom
2008-08-29 22:56 ` michael block
2008-08-29 18:42 ` Antonin Vecera
2008-08-29 19:20 ` plan9
2008-08-29 23:11 ` michael block
2008-08-29 23:42 ` Lyndon Nerenberg
2008-08-30 0:05 ` michael block
2008-08-30 0:10 ` Lyndon Nerenberg
2008-08-30 3:39 ` erik quanstrom
2008-08-30 1:25 ` michael block
2008-08-30 5:05 ` lucio [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=dab04424b8848545eb53dfb563094703@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).