mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ambx1@neo.rr.com (Adam Belay)
To: "Ville Syrjälä" <syrjala@sci.fi>
Cc: matthieu castet <castet.matthieu@free.fr>,
	jt@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] smsc-ircc2: Add PnP support.
Date: Thu, 18 Nov 2004 18:02:51 -0500	[thread overview]
Message-ID: <20041118230251.GK29574@neo.rr.com> (raw)
In-Reply-To: <20041118204145.GA21873@sci.fi>

On Thu, Nov 18, 2004 at 10:41:45PM +0200, Ville Syrjälä wrote:
> On Thu, Nov 18, 2004 at 08:49:50PM +0100, matthieu castet wrote:
> > Jean Tourrilhes wrote:
> > >On Thu, Nov 18, 2004 at 07:42:07PM +0100, matthieu castet wrote:
> > >>>>On3) If the ressources are markes as disabled, you just quit
> > >>>>with an error. Compouded with (2), this makes me doubly
> > >>>>nervous. Wouldn't it be possible to forcefully enable those 
> > >>
> > >>ressources ?
> > >>pnp should call automatiquely pnp_activate_dev() before probing the 
> > >>driver, so the resource should be activated. Have you got an example 
> > >>where the resource wheren't activated ?
> > >
> > >
> > >	No, it was more that I don't understand what PnP does for
> > >us. I don't have a SMS chipset to test on. Also, I would like to know
> > >if it remove the need of smcinit.
> > >
> > PnP is easy to understand ;)
> > When you probe a device, it will activate a device with the best 
> > configuration available.
> 
> So can we just remove the IORESOURCE_DISABLED tests?
> 
> And what about the pnp_*_valid() tests?
> 
> parport_pc (which I used as a guide) does both tests but 8250_pnp doesn't 
> do either.

Parport_pc uses them because resources could potentially be disabled, but the
parport could still be functional.  Therefore, it must check.  It is probably
ok to not check on most hardware.  Nonetheless, it's best to play it safe, and
always verify the resource configuration.

Thanks,
Adam

  reply	other threads:[~2004-11-18 23:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 18:42 matthieu castet
2004-11-18 18:55 ` Jean Tourrilhes
2004-11-18 19:49   ` matthieu castet
2004-11-18 20:41     ` Ville Syrjälä
2004-11-18 23:02       ` Adam Belay [this message]
2004-11-19 15:27 ` Meelis Roos
2004-11-19 15:53   ` matthieu castet
2004-11-19 15:57     ` matthieu castet
2004-11-19 16:15       ` Meelis Roos
2004-11-19 16:22       ` Meelis Roos
2004-11-19 17:28         ` matthieu castet
2004-11-19 17:34           ` Meelis Roos
2004-11-19 18:29             ` matthieu castet
2004-11-19 23:09               ` Meelis Roos
2004-11-20  9:50                 ` matthieu castet
2004-11-21 17:50                   ` Meelis Roos
2004-11-21 18:16                     ` matthieu castet
2004-11-21 18:51                       ` Meelis Roos
2004-11-21 19:21                         ` matthieu castet
2004-11-21 20:20                         ` matthieu castet
2004-11-22  1:29                           ` Li Shaohua
2004-11-22  8:37                             ` Meelis Roos
2004-11-26 16:02                               ` matthieu castet
2004-11-26 18:19                                 ` Meelis Roos
2004-11-27  0:50                                   ` matthieu castet
2004-11-27 12:15                                     ` Meelis Roos
2004-11-27 14:02                                       ` matthieu castet
2004-11-27 18:24                                         ` Meelis Roos
2004-11-27 18:58                                           ` matthieu castet
2004-11-27 19:25                                             ` matthieu castet
2004-11-27 19:39                                             ` Meelis Roos
2004-11-22  8:39                             ` Meelis Roos
2004-11-22  8:42                             ` Meelis Roos
2004-11-22  8:38                           ` Meelis Roos
2004-11-20 11:43                 ` [ACPI] " Ville Syrjälä
2004-11-20 11:57                   ` matthieu castet
     [not found] <20041117232047.GA28061@bougret.hpl.hp.com>
2004-11-18  3:52 ` Ville Syrjä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=20041118230251.GK29574@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=castet.matthieu@free.fr \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syrjala@sci.fi \
    /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

Powered by JetHome