[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#209301: modconf: on module installation failure, suggest isa-pnp.o to the user

#include <hallo.h>
* Ryan Underwood [Sun, Sep 14 2003, 10:27:40PM]:

> > > If the module itself is aware of isa-pnp, then yes, this is the case.
> > > However, consider this scenario:  The card is a PnP card, the driver is
> > > not PnP aware and would like to know the I/O and IRQ resources when
> > > loaded.  The card must first be configured by loading isa-pnp, and then
> > > the other driver can be loaded based on the resources that the card is
> > > assigned.
> > 
> > Nonsense, pure nonsence. Please read the isapnp_init function of isapnp.c
> > before claiming such thing. Then show me the place where random cards
> > are configured to random ressources by isa-pnp and the users gets
> > information about the ressources.
> Please refer to linux/Documentation/isapnp.txt:
> Write commands:
> ---------------
> With the write interface you can activate or modify the configuration of
> ISA Plug & Play devices.  It is mainly useful for drivers which have not
> been rewritten to use the ISA Plug & Play kernel support yet.

Sorry, what is your point? First, you tell us that isa-pnp module
configures the cards when loaded. Now, you show a way to *configure the
ressources manually* via the proc interface. Just for the case that you
missed it, we do already include isapnptools for pre-2.4 kernels. And
pnpdump&isapnp are a way more user-friendly and better documented than
the proc interface.

In der Mitte von Schwierigkeiten liegen die Möglichkeiten.
		-- Albert Einstein

Reply to: