All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: paulus@samba.org, linuxppc-embedded@ozlabs.org
Subject: Re: RFC/Commit: New ocp id for CANbus devs
Date: Wed, 09 Mar 2005 20:40:09 +0300	[thread overview]
Message-ID: <422F34F9.1050607@varma-el.com> (raw)
In-Reply-To: <d32d7ad858d3660f9d7fdf33003ca4cc@freescale.com>

Hi Kumar:
> Is this for 2.6?  
Oh sorry, certainly for 2.6 (Sylvain's kernel more precisely).
But since, Sylvain not maintainer of ocp_ids.h, so I send
this patch to Paul (who create it, am I right?).

> If so, 5200 needs to be moved to using the new driver 
> model and platform devices.  Take a look at support for MPC85xx or 
> marvell (mv64x60) as examples.
> 
> - kumar
Kumar, please, more cleanly, what did you want to say? If you told about
board_ocp[] in lite5200.c (platform specific). Then yes, I use it, but 
not mpc5200.c

--
Andrey

> 
> On Mar 9, 2005, at 6:20 AM, Andrey Volkov wrote:
> 
>> Hi Paul,
>>
>> Pls. commit this patch, its needed for MPC5200 Can
>>
>> Regards
>>  Andrey Volkov
>>
>> Signed-off-by: Andrey Volkov <avolkov@varma-el.com>
>>  --
>>  ChangeSet@1.2159, 2005-03-09 15:05:37+03:00, avolkov@varma-el.com
>>     ocp_ids.h:
>>       New number for onboard CANbus devs.
>>
>>
>>
>>   ocp_ids.h |    1 +
>>    1 files changed, 1 insertion(+)
>>
>>
>>
>> diff -Nru a/include/asm-ppc/ocp_ids.h b/include/asm-ppc/ocp_ids.h
>>  --- a/include/asm-ppc/ocp_ids.h 2005-03-09 15:07:51 +03:00
>>  +++ b/include/asm-ppc/ocp_ids.h 2005-03-09 15:07:51 +03:00
>>  @@ -62,6 +62,7 @@
>>    #define OCP_FUNC_RGMII                0x00D3
>>    #define OCP_FUNC_TAH          0x00D4
>>    #define OCP_FUNC_SEC2         0x00D5  /* Crypto/Security 2.0 */
>>  +#define OCP_FUNC_CAN           0x00D6  /* CAN bus device */
>>
>>   /* Network 0x0200 - 0x02FF */
>>    #define OCP_FUNC_EMAC         0x0200
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>>  Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 
> 

  reply	other threads:[~2005-03-09 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 12:20 RFC/Commit: New ocp id for CANbus devs Andrey Volkov
2005-03-09 17:16 ` Kumar Gala
2005-03-09 17:40   ` Andrey Volkov [this message]
2005-03-09 18:37     ` Sylvain Munaut
2005-03-09 19:24       ` Kumar Gala
     [not found]       ` <422F486A.2080104@varma-el.com>
     [not found]         ` <422F534A.1020107@246tNt.com>
2005-03-10  6:57           ` Andrey Volkov
2005-03-10  7:10             ` Kumar Gala
2005-03-10  7:35               ` Andrey Volkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=422F34F9.1050607@varma-el.com \
    --to=avolkov@varma-el.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.