What size would you suggest for a ram_console allocation?   I saw that
the G1 is using 128k...    That seems sufficient...   Any reason why I
should use more or less?
 
 
Thanks
 
Rob Stoddard
 
 
 

________________________________

From: Mike Lockwood [mailto:lockw...@google.com] 
Sent: Monday, January 05, 2009 12:05 PM
To: Dan Egnor; Stoddard Robert-JWND84
Cc: android-kernel
Subject: Re: [android-kernel] Re: ram_console driver and
/proc/last_kmsg... ram_console probe function never runs.


Hi Robert,

It sounds like you need to register your new driver in the board file.
For example, for the TMobile G1, you would edit the file
arch/arm/mach-msm/board-trout.c and add a platform_device struct with
name="ram_console" and add it to the list of platform devices in:

static struct platform_device *devices[] __initdata = {
    ...
};

Mike


On Mon, Jan 5, 2009 at 2:47 PM, Dan Egnor <eg...@google.com> wrote:


        [+android-kernel], who can probably help you here.
        
        
        On Mon, Jan 5, 2009 at 11:32 AM, Stoddard Robert-JWND84
<jwn...@motorola.com> wrote:
        

                I have been working on why I don't see a /proc/last_kmsg
file when I panic the Android/Linux kernel.  I have written a driver
which causes a kernel panic because my company requires functionality
for testing "exceptional" behavior of all types, including (especially)
kernel panics.  Unfortunately, when I panic the phone, the
/proc/last_kmsg file that contains the reason for the panic and other
debug data does not appear.  I have found that the ram_console driver
(android/kernel/drivers/android/ram_console.c) is responsible for
creating this file.  This driver is a platform_driver, about which
there's little information on the net.  This driver initializes using
the following code:
                 
                

                static struct platform_driver ram_console_driver = {
                        .probe = ram_console_driver_probe,
                        .driver         = {
                                .name   = "ram_console",
                        },
                };
                 
                static int __init ram_console_module_init(void)
                {
                        int err;
                        err =
platform_driver_register(&ram_console_driver);
                        return err;
                }
                
                 
                The init function given above runs, however the probe
function is never called.   I am wondering what's necessary to make this
probe function happen?  Is it only called when the ram_console survives
from the last run?
                 
                Thank you for your assistance
                 
                Rob Stoddard
                 




--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
-~----------~----~----~----~------~----~------~--~---

Reply via email to