From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kumar.gala@freescale.com>
Received: from de01egw01.freescale.net (de01egw01.freescale.net
	[192.88.165.102]) by ozlabs.org (Postfix) with ESMTP id 4B9E767A78
	for <linuxppc-embedded@ozlabs.org>;
	Thu, 10 Mar 2005 18:10:11 +1100 (EST)
In-Reply-To: <422FEFBE.4070903@varma-el.com>
References: <422FEFBE.4070903@varma-el.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <6bac59cd11e3d6fd005b8630e67bee33@freescale.com>
From: Kumar Gala <kumar.gala@freescale.com>
Date: Thu, 10 Mar 2005 01:10:08 -0600
To: "Andrey Volkov" <avolkov@varma-el.com>
Cc: Sylvain Munaut <tnt@246tNt.com>, paulus@samba.org,
	linuxppc-embedded@ozlabs.org
Subject: Re: RFC/Commit: New ocp id for CANbus devs
List-Id: Linux on Embedded PowerPC Developers Mail List
	<linuxppc-embedded.ozlabs.org>
List-Unsubscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-embedded>,
	<mailto:linuxppc-embedded-request@ozlabs.org?subject=unsubscribe>
List-Archive: <http://ozlabs.org/pipermail/linuxppc-embedded>
List-Post: <mailto:linuxppc-embedded@ozlabs.org>
List-Help: <mailto:linuxppc-embedded-request@ozlabs.org?subject=help>
List-Subscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-embedded>,
	<mailto:linuxppc-embedded-request@ozlabs.org?subject=subscribe>

I would assume you plan on moving your driver over to the driver model 
which will make all of this moot.

So I think Sylvain's suggestion of allocating a number for the time 
being makes the most sense until we get 52xx convert over to platform 
devices.

- kumar

On Mar 10, 2005, at 12:57 AM, Andrey Volkov wrote:

> Sylvain Munaut wrote:
>  >
> >> Sylvain, but what I wish now - only single number
>  >> (until driver will done).
>  >
> > If you only need a temporary ocp ID, just fix it youself in your 
> local
> > tree, no need to try to push that upstream.
>
> I already use it as temp, but I don't want pitfalls in future (when
>  smb. take this number).
>
> Also, since CAN ocp present not only in MPC5200, but, AFAIK, in another
> chips too, IMHO, it must be well known constant id.
>
> Regards
>  Andrey