From: Christoph Hellwig <hch@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Christoph Hellwig" <hch@infradead.org>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Dave Jones" <davej@redhat.com>,
"David Härdeman" <david@2gen.com>,
"lkml - Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Oops modprobing i830 with 2.6.8.1
Date: Wed, 18 Aug 2004 19:45:31 +0100 [thread overview]
Message-ID: <20040818194531.A1703@infradead.org> (raw)
In-Reply-To: <1092850671.26051.22.camel@localhost.localdomain>; from alan@lxorguk.ukuu.org.uk on Wed, Aug 18, 2004 at 06:37:51PM +0100
On Wed, Aug 18, 2004 at 06:37:51PM +0100, Alan Cox wrote:
> On Mer, 2004-08-18 at 19:28, Christoph Hellwig wrote:
> > Well, aic7xxx also works without a pci version of the card present, even
> > if you compile your kernel with PCI.. I don't want to say we should change
> > the driver to not work anymore if there's not agp support, but that the
> > driver shouldn't try to overengineeredly do all this runtime probing unlike
> > everyone else.
>
> Yes but PCI isnt a module that doesn't load if you have no supported AGP
> device
Well, if you want an example that exactly matches the drm situation look at
various driver with optional i2c support, like many of the fbdev ones.
next prev parent reply other threads:[~2004-08-18 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 22:08 Oops modprobing i830 with 2.6.8.1 David Härdeman
2004-08-17 23:37 ` Dave Jones
2004-08-17 23:43 ` Christoph Hellwig
2004-08-17 23:45 ` Dave Jones
2004-08-18 4:01 ` Rusty Russell
2004-08-18 9:15 ` Christoph Hellwig
2004-08-18 17:22 ` Alan Cox
2004-08-18 18:28 ` Christoph Hellwig
2004-08-18 17:37 ` Alan Cox
2004-08-18 18:45 ` Christoph Hellwig [this message]
2004-08-18 18:09 ` David Härdeman
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 10:11 Dave Airlie
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=20040818194531.A1703@infradead.org \
--to=hch@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=david@2gen.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.