From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Egbert Eich <eich@suse.de>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Xserver development <xorg@freedesktop.org>,
Egbert Eich <eich@pdx.freedesktop.org>
Subject: Re: [Linux-fbdev-devel] Re: Who is stomping PCI config space?
Date: Sun, 06 Mar 2005 09:42:19 +1100 [thread overview]
Message-ID: <1110062539.13594.74.camel@gaston> (raw)
In-Reply-To: <16938.847.772446.757968@xf14.local>
> How do we deal with interrupts from VGA cards that we don't have a
> driver for?
We don't get any, do we ? If we get an interrupt we don't have a driver
for, the system dies usually ;) Well, unless it's an edge interrupt, in
which case we can just drop it on the floor, but PCI interrupts are
level.
> We don't service interrupts in this case either.
> Can't we unregister the interrupt handler until everything
> is set up right? Maybe a dump idea...
> Also there is a generic VGA register to control interrupts.
We have reached the end of my VGA knowledge, but I seriously doubt a VGA
card will issue interrupts if not previously programmed to do so... So
we probably don't have to bother. We only care about interrupts that we
have a use for, that is interrupts triggered by cards upon request of
their driver, for things like DMA/AGP command buffer operations, vblank,
monitor detection, ...
Ben.
next prev parent reply other threads:[~2005-03-05 22:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 19:03 Who is stomping PCI config space? Jon Smirl
2005-03-03 23:07 ` Benjamin Herrenschmidt
2005-03-04 0:15 ` Jon Smirl
2005-03-04 3:03 ` Jon Smirl
2005-03-04 6:40 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-04 12:07 ` Egbert Eich
2005-03-04 17:35 ` Jon Smirl
2005-03-04 22:42 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-05 19:06 ` Egbert Eich
2005-03-05 22:42 ` Benjamin Herrenschmidt [this message]
2005-03-07 11:19 ` Egbert Eich
2005-03-08 3:21 ` Benjamin Herrenschmidt
2005-03-05 17:33 ` Egbert Eich
2005-03-04 17:58 ` Jon Smirl
2005-03-04 22:45 ` Benjamin Herrenschmidt
2005-03-05 19:07 ` Egbert Eich
2005-03-05 22:43 ` Benjamin Herrenschmidt
2005-03-04 22:27 ` Benjamin Herrenschmidt
2005-03-05 18:26 ` Egbert Eich
2005-03-05 22:39 ` Benjamin Herrenschmidt
2005-03-07 11:05 ` Egbert Eich
2005-03-04 12:02 ` Egbert Eich
2005-03-04 11:25 ` Egbert Eich
2005-03-04 22:16 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-05 17:36 ` Egbert Eich
2005-03-04 11:12 ` Egbert Eich
2005-03-04 22:51 ` Benjamin Herrenschmidt
[not found] ` <42278AEC.4080706@dunaweb.hu>
2005-03-04 11:21 ` Egbert Eich
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=1110062539.13594.74.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=eich@pdx.freedesktop.org \
--cc=eich@suse.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=xorg@freedesktop.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).