From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664.
Date: Thu, 17 Jan 2008 14:52:50 +0200 [thread overview]
Message-ID: <1012527691.20080117145250@gmail.com> (raw)
In-Reply-To: <478F4876.9030405@student.utwente.nl>
Hello Koen,
Thursday, January 17, 2008, 2:22:14 PM, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Paul Sokolovsky schreef:
> | How workarounds for specific buggy wifi cards relate to a generic APM
> | daemon? Or from other side, why everyone should endure more latency
> | during suspend/resume, with that latency already being >1s, because 5%
> | or less of those "everyone" use buggy cards?
> |
> | Please move this workaround to a packages of the buggy driver, or to a
> | separate package which is RDEPEND'ed by buggy driver. See
> | bluez-dtl1-workaround_1.0.bb for similar conversion performed.
> IIRC this is a workaround for cards that have their firmware in RAM
> (i.e. almost all hostap cards). They loose their firmware on suspend and
> our scripts don't reload it. This is actually a bug in our firmware
> loading scripts and I think this solution is acceptable medium-term, but
> ~ longterm we should fix our firmware loading scripts.
Ok, no problem. There're lots of broken hardware and drivers around,
and of course they need to be supported still, and right now. The question
is how that is done - if it comes mixed into one big mess, we won't have
nice working system at all. And as someone who makes small steps towards
clearing this stuff (all the fixes I already did to udev and apmd to
get rid of device-specific hacks in them), I don't appreciate someone
moving in the opposite direction just to solve on-spot problem. OE is
powerful environment allowing to solve make focused, maintainable and
reusable changes - even if they're workarounds, and people should
learn to use them.
> regards,
> Koen
[]
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2008-01-17 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1JF7vM-0000k1-Mc@linuxtogo.org>
2008-01-17 11:18 ` [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664 Paul Sokolovsky
2008-01-17 11:57 ` Bug ohviey1
2008-01-17 12:01 ` [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664 Michael 'Mickey' Lauer
2008-01-17 12:22 ` Koen Kooi
2008-01-17 12:52 ` Paul Sokolovsky [this message]
2008-01-17 14:34 ` Rolf Leggewie
2008-01-17 15:09 ` Mike (mwester)
2008-01-17 15:59 ` Paul Sokolovsky
2008-01-17 17:52 ` Mike (mwester)
2008-01-17 15:23 ` Paul Sokolovsky
2008-01-18 17:33 ` Rolf Leggewie
2008-01-19 18:29 ` Paul Sokolovsky
2008-01-21 11:16 ` Rolf Leggewie
2008-01-18 18:28 ` Rolf Leggewie
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=1012527691.20080117145250@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.