linux-kernel - Re: ramoops: is using platform

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4DDBE4D5.9010000@gmail.com>
Date:	Tue, 24 May 2011 19:03:17 +0200
From:	Marco Stornelli <marco.stornelli@...il.com>
To:	Stevie Trujillo <stevie.trujillo@...il.com>
CC:	linux-kernel@...r.kernel.org, xiyou.wangcong@...il.com,
	kmpark@...radead.org
Subject: Re: ramoops: is using platform_drivers correct?

Il 23/05/2011 15:27, Stevie Trujillo ha scritto:
> Hello,
>
> ramoops (drivers/char/ramoops.c) is for "all" computers right? When I try to

Yes, or at least was my intention. It's true that this drivers is useful 
when you use an NVRAM, this is typical for the embedded world where the 
platform driver approach is more diffused. Sure at this point the module 
parameters are not useful. In addition the platform data struct doesn't 
define a way to select if to dump only oops. At the end I think a patch 
it's needed here. I have to look at the code to see if it's possible to 
use the platform data OR module parameters. I'll submit a patch.

Marco
--
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/