From: "Steven A. DuChene" <sduchene@mindspring.com>
To: Thomas Hood <jdthood@mail.com>
Cc: "Steven A. DuChene" <sduchene@mindspring.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP BIOS -- bugfix; update devlist on setpnp
Date: Wed, 17 Oct 2001 12:08:12 -0400 [thread overview]
Message-ID: <20011017120812.E2015@lapsony.mydomain.here> (raw)
In-Reply-To: <1003288485.14282.100.camel@thanatos> <20011017041014.B2015@lapsony.mydomain.here> <1003325742.12542.164.camel@thanatos>
In-Reply-To: <1003325742.12542.164.camel@thanatos>; from jdthood@mail.com on Wed, Oct 17, 2001 at 09:35:34AM -0400
On Wed, Oct 17, 2001 at 09:35:34AM -0400, Thomas Hood wrote:
> On Wed, 2001-10-17 at 04:10, Steven A. DuChene wrote:
> > OK, I tried this with the Intel STL2 motherboard I also have and I got
> > a similar error when trying to load the correct i2c bus module when the
> > PnPBIOS stuff is compiled into the kernel.
>
> Understood.
>
> I'd just like to reiterate that my patch isn't the cause
> of your problem. It's just that my patch doesn't address
> your problem. IIUC.
Yes, I understood that from the start of all of this but you seemed to be
be the only person messing with the PnPBIOS code so I thought you might be
interested in this annomoly. I appreciate the info/help you have provided
so far.
>
> I provided a "workaround patch" before. Can you continue
> to use that for the time being?
>
Yes, but according to these latest results that work around of skipping a
particular ioport would have to be different for each motherboard with this
problem. There must be a better way to do this.
> I'd like to make a promise that I'll submit a new patch
> soon that will address your problem; however I don't yet know
> exactly how to go about addressing it.
>
Perhaps someone else can provide us a hint or two as to where to start. :-)
--
Steven A. DuChene sad@ale.org
linux-clusters@mindspring.com
sduchene@mindspring.com
http://www.mindspring.com/~sduchene/
next prev parent reply other threads:[~2001-10-17 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 3:14 Thomas Hood
2001-10-17 8:10 ` Steven A. DuChene
2001-10-17 16:04 ` Gunther Mayer
2001-10-17 20:58 ` Thomas Hood
2001-10-17 13:35 ` Thomas Hood
2001-10-17 16:08 ` Steven A. DuChene [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-13 15:40 Thomas Hood
2001-10-15 6:37 ` Jurgen Botz
2001-10-15 9:45 ` Stelian Pop
2001-10-15 12:01 ` Andrey Panin
2001-10-15 12:25 ` Alan Cox
2001-10-15 21:49 ` Thomas Hood
2001-10-15 14:15 ` Ion Badulescu
2001-10-17 2:48 ` Steven A. DuChene
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=20011017120812.E2015@lapsony.mydomain.here \
--to=sduchene@mindspring.com \
--cc=jdthood@mail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®