Hi!
> > Still, what we definitely want is _one single_ architecture independent
> > whitelist. And there is where hal-info comes in which is easy to update
> > for distributions etc. IMHO. I'm seeing this difficulty with the two
> > different lists for quite some time know and thought about possib
On Thu 03. May - 18:45:10, David Zeuthen wrote:
> On Fri, 2007-05-04 at 00:12 +0200, Holger Macht wrote:
> > Still, what we definitely want is _one single_ architecture independent
> > whitelist. And there is where hal-info comes in which is easy to update
> > for distributions etc. IMHO. I'm seein
On Fri, 2007-05-04 at 00:12 +0200, Holger Macht wrote:
> Still, what we definitely want is _one single_ architecture independent
> whitelist. And there is where hal-info comes in which is easy to update
> for distributions etc. IMHO. I'm seeing this difficulty with the two
> different lists for qui
On Fri 04. May - 00:12:24, Holger Macht wrote:
> On Thu 03. May - 21:55:14, Danny Kukawka wrote:
> > On Donnerstag, 3. Mai 2007, David Zeuthen wrote:
> > > On Thu, 2007-05-03 at 10:40 +0200, Danny Kukawka wrote:
> > > > The point is not using s2ram or that s2ram would break. The point is
> > > > t
On Thu 03. May - 21:55:14, Danny Kukawka wrote:
> On Donnerstag, 3. Mai 2007, David Zeuthen wrote:
> > On Thu, 2007-05-03 at 10:40 +0200, Danny Kukawka wrote:
> > > The point is not using s2ram or that s2ram would break. The point is that
> > > removing the quirk would break resume if you suspend v
On Donnerstag, 3. Mai 2007, David Zeuthen wrote:
> On Thu, 2007-05-03 at 10:40 +0200, Danny Kukawka wrote:
> > The point is not using s2ram or that s2ram would break. The point is that
> > removing the quirk would break resume if you suspend via init=/bin/bash
> > (the testcase) or console. This ch
