From: Helge Deller <deller@gmx.de>
To: Grant Grundler <grundler@puffin.external.hp.com>,
Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] iotree thoughts
Date: Tue, 21 Aug 2001 23:12:09 +0200 [thread overview]
Message-ID: <20010821211222.70853482A@dsl2.external.hp.com> (raw)
In-Reply-To: <200108210753.BAA21158@puffin.external.hp.com>
On Tuesday 21 August 2001 09:53, Grant Grundler wrote:
> Matthew Wilcox wrote:
> > Only if they're called. The majority of places where these functions
> > exist can provably never be called. The others probably won't be :-)
>
> I don't bet on "probably".
>
> If the kernel is designed to not link when a dependency is not met,
> I can find problems much faster when they arise. Having to build/reboot
> to find porting/coding issues seems harder than it needs to be.
Hi Grant & Matthew,
I still think Matthew's solution is a good idea. Why should the user be
bothered to compile in that PCI stuff if he won't need it at all ?
I tried Matthew's patch and it worked without problems on my 715/64
and this is exactlly one of those machines for which the patch was
designed. Those machines use LASI-style LAN, PS/2 or HIL Keyboard/Mice,
STI(fb) and the harmony sound driver. Those are well-defined drivers which we
know that they work without PCI and which other drivers should we need ?
GSC-cards ? They should work since I think they only have additional LASI's
or somethink like that (You may correct me if I'm wrong.).
EISA-Cards ? We don't support any yet. Maybe in the future, but then the user
will also need to add PCI support anyway.
So I don't see any reason, why we shouldn't make it possible to link
a kernel without PCI support and call BUG() (and print out the port-number as
Alan suggested) just in case we would miss one place.
Btw, I love a small kernel if I'm running it on such a slow machine which is often
only equipped with 32-64 MB RAM.
Just my 0.02 cents,
Helge
next prev parent reply other threads:[~2001-08-21 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 1:05 [parisc-linux] iotree thoughts Matthew Wilcox
2001-08-09 15:06 ` Grant Grundler
2001-08-10 0:37 ` [parisc-linux] Installation Gururaj Ananthateerta
2001-08-10 2:04 ` Thomas Marteau
2001-08-14 16:02 ` [parisc-linux] iotree thoughts Matthew Wilcox
2001-08-21 5:44 ` Grant Grundler
2001-08-21 7:09 ` Matthew Wilcox
2001-08-21 7:53 ` Grant Grundler
2001-08-21 21:12 ` Helge Deller [this message]
2001-08-21 14:12 ` Alan Cox
2001-08-22 0:50 ` Matthew Wilcox
2001-08-25 5:59 ` Grant Grundler
2001-08-27 19:20 ` Matthew Wilcox
[not found] <200108212111.PAA28876@puffin.external.hp.com>
2001-08-23 6:18 ` Grant Grundler
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=20010821211222.70853482A@dsl2.external.hp.com \
--to=deller@gmx.de \
--cc=grundler@puffin.external.hp.com \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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