All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Ingo Molnar <mingo@elte.hu>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	x86@kernel.org
Subject: Re: Dell Studio 1536 needs pci=nocrs to boot.
Date: Fri, 6 Jan 2012 12:57:58 -0500	[thread overview]
Message-ID: <20120106175757.GA16807@redhat.com> (raw)
In-Reply-To: <CAErSpo6S19rznjbkos3LPk8K9GK=kFUr9+OqRfeZ72TiJpj35Q@mail.gmail.com>

On Fri, Jan 06, 2012 at 10:32:14AM -0700, Bjorn Helgaas wrote:

 > > There's at least one more dell (Seems that entire 'studio' product line
 > > is affected) that I'm waiting on DMI data from.
 > > Also a thinkpad that I have a patch pending for.
 > 
 > I think we should drop the Dell 1536 blacklist entry from this patch
 > (adding set_nouse_crs() itself is fine and may be needed for other
 > machines).
 > 
 > The patches here: https://lkml.org/lkml/2012/1/5/402 should cover the
 > Dell 1536 issue as well as the Dell 1546 and any others with the same
 > BIOS defect.

Sounds good to me.

	Dave


  reply	other threads:[~2012-01-06 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30 19:37 Dell Studio 1536 needs pci=nocrs to boot Dave Jones
2012-01-01 14:53 ` Ingo Molnar
2012-01-03 17:30   ` Jesse Barnes
2012-01-03 17:55     ` Bjorn Helgaas
2012-01-03 18:00       ` Dave Jones
2012-01-06 17:32         ` Bjorn Helgaas
2012-01-06 17:57           ` Dave Jones [this message]
2012-01-06 20:10             ` Jesse Barnes
2012-01-04 16:33       ` Add Dell Studio 1557 to pci=nocrs blacklist Dave Jones
2012-01-04 17:08         ` Jesse Barnes
2012-01-04 18:37         ` Ingo Molnar
2012-01-11 16:07           ` Bjorn Helgaas

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=20120106175757.GA16807@redhat.com \
    --to=davej@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@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 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.