All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: Alex Williamson <alex.williamson@hp.com>
Cc: torvalds@osdl.org, akpm@osdl.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	sensors@Stimpy.netroedge.com
Subject: [BK PATCH] I2C update for 2.6.8-rc1
Date: Thu, 19 May 2005 06:25:12 +0000	[thread overview]
Message-ID: <20040824220450.GE11165@kroah.com> (raw)
In-Reply-To: <1093384722.8445.10.camel@tdi>

On Tue, Aug 24, 2004 at 03:58:42PM -0600, Alex Williamson wrote:
> On Wed, 2004-07-14 at 17:05 -0700, Greg KH wrote:
> 
> > <orange:fobie.net>:
> >   o I2C: patch quirks.c - SMBus hidden on hp laptop
> 
>    This particular patch, along w/ the new 20040715 ACPI drop has made
> my nc6000 laptop unusable.  The problem is we're exposing a device that
> firmware considers hidden.  The new motherboard driver in ACPI goes out
> and tries to claim resources to prevent them from being stepped on.  It
> rightfully considers the hidden SMBus device a motherboard resource.
> The PCI code then stumbles onto this device, sees that the BAR it's
> using is unavailable and moves it somewhere else in the address space.
> At this point, I lose two for the three thermal zones on the laptop
> because the AML that deals with them assumes they haven't moved.
> 
>    I'm not sure what the point on un-hiding this devices it.  ACPI sets
> up an OpRegion to access this device and should have exclusive access to
> that region.  Letting a sensor driver poke at it may be fun, but I'd
> rather not fry my laptop.  Can we drop the un-hiding of the SMBus for
> this laptop (probably the nc8000 too), or is there some way to make the
> ACPI motherboard driver and this quirk live together?  Thanks,

See the bugzilla.kernel.org bug #3191 for more information.

If someone can come up with a patch that works for everyone, I'll be
glad to apply it.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: torvalds@osdl.org, akpm@osdl.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	sensors@Stimpy.netroedge.com
Subject: Re: [BK PATCH] I2C update for 2.6.8-rc1
Date: Tue, 24 Aug 2004 15:04:50 -0700	[thread overview]
Message-ID: <20040824220450.GE11165@kroah.com> (raw)
In-Reply-To: <1093384722.8445.10.camel@tdi>

On Tue, Aug 24, 2004 at 03:58:42PM -0600, Alex Williamson wrote:
> On Wed, 2004-07-14 at 17:05 -0700, Greg KH wrote:
> 
> > <orange:fobie.net>:
> >   o I2C: patch quirks.c - SMBus hidden on hp laptop
> 
>    This particular patch, along w/ the new 20040715 ACPI drop has made
> my nc6000 laptop unusable.  The problem is we're exposing a device that
> firmware considers hidden.  The new motherboard driver in ACPI goes out
> and tries to claim resources to prevent them from being stepped on.  It
> rightfully considers the hidden SMBus device a motherboard resource.
> The PCI code then stumbles onto this device, sees that the BAR it's
> using is unavailable and moves it somewhere else in the address space.
> At this point, I lose two for the three thermal zones on the laptop
> because the AML that deals with them assumes they haven't moved.
> 
>    I'm not sure what the point on un-hiding this devices it.  ACPI sets
> up an OpRegion to access this device and should have exclusive access to
> that region.  Letting a sensor driver poke at it may be fun, but I'd
> rather not fry my laptop.  Can we drop the un-hiding of the SMBus for
> this laptop (probably the nc8000 too), or is there some way to make the
> ACPI motherboard driver and this quirk live together?  Thanks,

See the bugzilla.kernel.org bug #3191 for more information.

If someone can come up with a patch that works for everyone, I'll be
glad to apply it.

thanks,

greg k-h

  reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15  0:05 [BK PATCH] I2C update for 2.6.8-rc1 Greg KH
2005-05-19  6:25 ` Greg KH
2004-07-15  0:07 ` [PATCH] " Greg KH
2004-07-15  0:07   ` Greg KH
2005-05-19  6:25     ` Greg KH
2004-07-15  0:07     ` Greg KH
2005-05-19  6:25       ` Greg KH
2004-07-15  0:07       ` Greg KH
2005-05-19  6:25         ` Greg KH
2004-07-15  0:07         ` Greg KH
2005-05-19  6:25           ` Greg KH
2004-07-15  0:07           ` Greg KH
2005-05-19  6:25             ` Greg KH
2004-07-15  0:07             ` Greg KH
2004-07-15  0:07               ` Greg KH
2005-05-19  6:25                 ` Greg KH
2004-07-15  0:07                 ` Greg KH
2004-07-15  0:07                   ` Greg KH
2005-05-19  6:25                     ` Greg KH
2004-07-15  0:07                     ` Greg KH
2005-05-19  6:25                       ` Greg KH
2004-07-15  0:07                       ` Greg KH
2004-07-15  0:07                         ` Greg KH
2005-05-19  6:25                           ` Greg KH
2004-07-15  0:07                           ` Greg KH
2005-05-19  6:25                             ` Greg KH
2004-07-15  0:07                             ` Greg KH
2005-05-19  6:25                               ` Greg KH
2004-07-16 17:07                         ` Pavel Machek
2005-05-19  6:25                           ` Pavel Machek
2004-07-16 17:17                           ` Greg KH
2005-05-19  6:25                             ` Greg KH
2004-07-16 17:39                             ` Bob Riegelmann
2005-05-19  6:25                               ` Bob Riegelmann
2004-07-16 18:19                             ` Adam Kropelin
2005-05-19  6:25                               ` Adam Kropelin
2005-05-19  6:25     ` Greg KH
2005-05-19  6:25     ` Greg KH
2005-05-19  6:25     ` Jean Delvare
2005-05-19  6:25     ` Philip Pokorny
2004-07-17 14:30 ` Greg (or anyone else) one small i2c question Reinder
2004-07-30  5:40   ` --- " Reinder
2004-07-30  6:30     ` Denis Vlasenko
2004-08-25  6:44   ` Greg " Greg KH
2004-08-24 21:58 ` [BK PATCH] I2C update for 2.6.8-rc1 Alex Williamson
2005-05-19  6:25   ` Alex Williamson
2004-08-24 22:04   ` Greg KH [this message]
2005-05-19  6:25     ` Greg KH
2004-08-25  0:37     ` Linus Torvalds
2005-05-19  6:25       ` Linus Torvalds
2004-08-25  1:38       ` Alex Williamson
2005-05-19  6:25         ` Alex Williamson
2004-08-25  1:42         ` Alex Williamson
2005-05-19  6:25           ` Alex Williamson
2004-08-25  2:02         ` Linus Torvalds
2005-05-19  6:25           ` Linus Torvalds
2004-08-25  6:14           ` Greg KH
2005-05-19  6:25             ` Greg KH
2004-08-25  6:36             ` Greg KH
2005-05-19  6:25               ` Greg KH

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=20040824220450.GE11165@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=alex.williamson@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@Stimpy.netroedge.com \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.