linux-kernel - Re: [PATCH 3/3] ACPI autoloading - Create __mod_acpi_device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070704073342.GC8338@inferi.kami.home>
Date:	Wed, 4 Jul 2007 16:33:42 +0900
From:	Mattia Dongili <malattia@...ux.it>
To:	Len Brown <lenb@...nel.org>
Cc:	trenn@...e.de, linux-kernel <linux-kernel@...r.kernel.org>,
	linux-acpi <linux-acpi@...r.kernel.org>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	acpi4asus-user <acpi4asus-user@...ts.sourceforge.net>
Subject: Re: [PATCH 3/3] ACPI autoloading - Create __mod_acpi_device_table symbol for all acpi drivers.

On Tue, Jul 03, 2007 at 03:15:33AM -0400, Len Brown wrote:
> 
> > BTW: I also saw a laptop (IIRC it was a sony) with asus and sony ACPI
> > device.
> > When both drivers got loaded things broke.
> > A solution was to only let the asus driver get active if the device is
> > known. Currently, not sure whether still (I sent a patch a while ago),
> > the Asus driver falls back to a default ("M6N"?) configuration. IMO this
> > is a bit too dangerous and instead a message like "unsupported ASUS
> > model found, please send acpidump to linux-acpi@...r.kernel.org".
> 
> This is pretty scary.
> Can you drop the acpidump output into a bugzilla?

and add myself to the cc-list?

thanks
-- 
mattia
:wq!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/