From: Eric Valette <eric.valette@free.fr>
To: Alessandro Suardi <alessandro.suardi@gmail.com>
Cc: Felipe Balbi <me@felipebalbi.com>,
Alan Stern <stern@rowland.harvard.edu>,
Randy Dunlap <rdunlap@xenotime.net>,
lud <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.37-rc7: no more shutdown on DELL E6400
Date: Sat, 25 Dec 2010 16:58:25 +0100 [thread overview]
Message-ID: <201012251658.25928.eric.valette@free.fr> (raw)
In-Reply-To: <AANLkTik9ByQpPCf3jNsotB__a_p3JxaiK7fA-E-K91U3@mail.gmail.com>
On Saturday 25 December 2010 00:42:58 Alessandro Suardi wrote:
> > No. Mine has an Intel WiFi chipset. With DELL the same reference can be
> > used for multiple different hardware instantiation (I have a nvidia vido
> > chipset some seems now to have an intel one).
> >
> Just as a data point, my Dell E6400 still shuts down fine in both
> 2.6.37-rc7 and -rc7-git2. This one has integrated Intel video (i915) and I
> use the out-of-tree broadcom-sta driver for the wireless interface. If
> needed, I can post my .config in the bugzilla entry (but won't, unless
> asked - in order to avoid possible bug noise).
That illustrates if needed the DELL reference multiple hardware problem. I put
2.6.37-rc7 (git1/git2) on my personnal laptop and I do not experience the
shutdown problem either.
I hope the problem is rare enough as I cannot supply more information before
getting back to work.
-- eric
prev parent reply other threads:[~2010-12-25 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 9:55 2.6.37-rc7: no more shutdown on DELL E6400 Eric Valette
2010-12-23 22:02 ` Randy Dunlap
2010-12-23 22:06 ` Eric Valette
2010-12-23 22:10 ` Randy Dunlap
2010-12-23 22:19 ` Eric Valette
2010-12-23 22:57 ` Alan Stern
2010-12-23 23:56 ` Felipe Balbi
2010-12-24 7:47 ` Eric Valette
2010-12-24 23:42 ` Alessandro Suardi
2010-12-25 15:58 ` Eric Valette [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:
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=201012251658.25928.eric.valette@free.fr \
--to=eric.valette@free.fr \
--cc=alessandro.suardi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=rdunlap@xenotime.net \
--cc=stern@rowland.harvard.edu \
/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