From: Jon Smirl <jonsmirl@gmail.com>
To: Adam Belay <abelay@novell.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@sgi.com>
Subject: Re: [RFC] PCI bridge driver rewrite
Date: Thu, 24 Feb 2005 02:25:12 -0500 [thread overview]
Message-ID: <9e4733910502232325118c9ff3@mail.gmail.com> (raw)
In-Reply-To: <1109228638.28403.71.camel@localhost.localdomain>
When you start writing the PCI root bridge driver you'll run into the
AGP drivers that are already attached to the bridge. I was surprised
by this since I expected AGP to be attached to the AGP bridge but now
I learned that it is a root bridge function.
An ISA LPC bridge driver would be nice too. It would let you turn off
serial ports, etc and let other systems know how many ports there are.
No real need for this, just a nice toy.
Does this work to cause a probe based on PCI class?
static struct pci_device_id p2p_id_tbl[] = {
{ PCI_DEVICE_CLASS(PCI_CLASS_BRIDGE_PCI << 8, 0xffff00) },
{ 0 },
};
I would like to install a driver that gets called whenever new
CLASS_VGA hardware shows up via hotplug. It won't attach to the
device, it will just add some sysfs attributes. The framebuffer
drivers need to attach the device. If I add attributes this way how
can I remove them?
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-02-24 7:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 6:22 [RFC] PCI bridge driver rewrite Adam Belay
2005-02-24 6:45 ` Jon Smirl
2005-02-24 7:03 ` Adam Belay
2005-02-24 7:25 ` Jon Smirl [this message]
2005-02-28 23:39 ` Adam Belay
2005-02-24 23:02 ` Jesse Barnes
2005-02-28 23:27 ` Adam Belay
2005-02-28 23:38 ` Jesse Barnes
2005-03-01 0:13 ` Adam Belay
2005-03-01 0:34 ` Jesse Barnes
2005-02-24 10:03 ` Russell King
2005-02-28 23:50 ` Adam Belay
2005-02-25 23:38 ` Greg KH
2005-02-28 23:58 ` Adam Belay
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 16:33 Nguyen, Tom L
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=9e4733910502232325118c9ff3@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=abelay@novell.com \
--cc=greg@kroah.com \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.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