LKML Archive on
help / color / mirror / Atom feed
From: Rene Herman <>
Cc: Len Brown <>, Dave Jones <>,, Adam M Belay <>,
	Zhao Yakui <>,
	Li Shaohua <>,
	Bjorn Helgaas <>,
	Linux Kernel <>
Subject: Re: PNP: dynamic pnp resources
Date: Mon, 17 Mar 2008 23:31:27 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 13-03-08 13:04, Thomas Renninger wrote:

> I had the problem that I could not test on isa systems.

Perhaps we can go organize a fundraiser for SuSE so they can go out and buy 
an ISAPnP soundcard. I have a few I can sell. I promise I won't overcharge 
them (much).

> Rene Herman helped here a lot.
> There are still open issues, last state was (comment from Rene):
> ------------------------
> No. Please note we're talking about ISAPnP, not PnPBIOS. No BIOS
> involved at all.
> Driver (sound/isa/cs423x/cs4236.c) furthermore does not use anything but
> the PnP layer itself. Start at snd_cs423x_pnpc_detect, which is the
> pnp .probe() method.
> I'll look into providing a more extensive answer and/or test whatever
> comes in later.
> -------------------------

Did look, but decided there wasn't much more specifically to add. It's 
something more fundamental about the flow of things and while the comment 
above is obviously cynical I did grow a bit tired of a series of patches 
that just transported the OOPS two lines down again each time, so I held out 
for Bjorn as well.

Still availabe for tests.


      parent reply	other threads:[~2008-03-17 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 15:14 PNP: increase the maximum number of resources Dave Jones
2008-03-12 17:08 ` Olivier Galibert
2008-03-12 17:45 ` Len Brown
2008-03-13  0:16   ` Rene Herman
2008-03-13 12:04   ` PNP: dynamic pnp resources Thomas Renninger
2008-03-13 15:17     ` Bjorn Helgaas
2008-03-17 22:31     ` Rene Herman [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).