From: Andrey Rahmatullin <wrar@altlinux.org>
To: Corentin Chary <corentincj@iksaif.net>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
Luca Niccoli <lultimouomo@gmail.com>,
Len Brown <len.brown@intel.com>,
Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
Matthew Garrett <mjg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] eeepc-laptop: don't enable camera at startup if it's already on.
Date: Tue, 20 Oct 2009 14:35:55 +0600 [thread overview]
Message-ID: <20091020083555.GG19095@wrars-comp.wrarsdomain> (raw)
In-Reply-To: <1255724567-25597-3-git-send-email-corentincj@iksaif.net>
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
On Fri, Oct 16, 2009 at 10:22:47PM +0200, Corentin Chary wrote:
> Switching the camera takes 500ms, checking if it's on is almost free...
So if I don't want camera to be enabled, I should wait 500ms on boot to
enable it and then other 500ms to disable?
--
WBR, wRAR (ALT Linux Team)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2009-10-20 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 20:22 [PATCH 0/2] eeepc-laptop updates for 2.6.32-rcX Corentin Chary
2009-10-16 20:22 ` [PATCH 1/2] Revert "eeepc-laptop: Prevent a panic when disabling RT2860 wireless when associated" Corentin Chary
2009-10-16 20:22 ` [PATCH 2/2] eeepc-laptop: don't enable camera at startup if it's already on Corentin Chary
2009-10-20 8:35 ` Andrey Rahmatullin [this message]
2009-10-20 9:04 ` Alan Jenkins
2009-10-20 9:24 ` Andrey Rahmatullin
2009-10-20 9:38 ` Alan Jenkins
2009-10-20 9:41 ` Andrey Rahmatullin
2009-10-20 14:19 ` Alan Jenkins
2009-10-20 14:31 ` Luca Niccoli
2009-10-20 10:06 ` Luca Niccoli
2009-11-03 15:25 ` Len Brown
2009-11-03 15:25 ` [PATCH 1/2] Revert "eeepc-laptop: Prevent a panic when disabling RT2860 wireless when associated" Len Brown
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=20091020083555.GG19095@wrars-comp.wrarsdomain \
--to=wrar@altlinux.org \
--cc=akpm@linux-foundation.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=corentincj@iksaif.net \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lultimouomo@gmail.com \
--cc=mjg@redhat.com \
/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