From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by ozlabs.org (Postfix) with SMTP id 4FEADDDDE1 for ; Mon, 20 Oct 2008 09:28:09 +1100 (EST) Date: Mon, 20 Oct 2008 00:28:09 +0200 (CEST) From: Guennadi Liakhovetski To: Jon Smirl Subject: Re: [PATCH] powerpc: enable heap randomization for linkstations In-Reply-To: <9e4733910810191505u3ec1db0dl25e87bf3b78c740d@mail.gmail.com> Message-ID: References: <20081013040703.GA11059@ime.usp.br> <20081013045116.GA11637@ime.usp.br> <20081013184443.GA20612@ld0162-tx32.am.freescale.net> <20081019025323.GA7887@ime.usp.br> <9e4733910810191432o58d204adw490cb8e4fcc390ac@mail.gmail.com> <9e4733910810191505u3ec1db0dl25e87bf3b78c740d@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: =?ISO-8859-1?Q?Rog=E9rio_Brito?= , Scott Wood , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, 19 Oct 2008, Jon Smirl wrote: > i2c-mpc.c has: > > static const struct of_device_id mpc_i2c_of_match[] = { > {.compatible = "fsl-i2c",}, > {}, > }; > MODULE_DEVICE_TABLE(of, mpc_i2c_of_match); > > > /* Structure for a device driver */ > static struct of_platform_driver mpc_i2c_driver = { > .match_table = mpc_i2c_of_match, > .probe = fsl_i2c_probe, > .remove = __devexit_p(fsl_i2c_remove), > .driver = { > .owner = THIS_MODULE, > .name = DRV_NAME, > }, > }; > > That should match: > > i2c@80003000 { > #address-cells = <1>; > #size-cells = <0>; > cell-index = <0>; > compatible = "fsl-i2c"; > reg = <0x80003000 0x1000>; > interrupts = <5 2>; > interrupt-parent = <&mpic>; > > rtc@32 { > device_type = "rtc"; > compatible = "ricoh,rs5c372a"; > reg = <0x32>; > }; > }; It should, but it doesn't. > This code works on my mpc5200 board. Don't know which 5200 board you have, but, for example lite5200 has compatible = "fsl,mpc5200-i2c","fsl-i2c"; see the difference? > Maybe fsl_i2c_probe() is failing? It has a printk at each error case (ok, except kzalloc, but I don't think that is the case), I see none of them. > Add some printks in i2c-mpc to help debug the problem. > Any errors from i2c-mpc in dmesg? None, and, as I said, there are no error messages from it, so, it doesn't get called at all. To be quite sure I added a printk at the entry - as expected it didn't get printed. Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer