From: Kumar Gala <kumar.gala@freescale.com>
To: "Sylvain Munaut" <tnt@246tNt.com>
Cc: paulus@samba.org, linuxppc-embedded@ozlabs.org
Subject: Re: RFC/Commit: New ocp id for CANbus devs
Date: Wed, 9 Mar 2005 13:24:35 -0600 [thread overview]
Message-ID: <22bb842e4ff1ada507be76703dda06f9@freescale.com> (raw)
In-Reply-To: <422F4284.1050806@246tNt.com>
Sylvain,
Thanks, the i2c driver that you used on the OCP side should work for=20
you on the platform device side as well. Also, do you plan on using=20
the ppc_sys stuff for this? Hopefully yes.
- kumar
On Mar 9, 2005, at 12:37 PM, Sylvain Munaut wrote:
> Andrey Volkov wrote:
>
> > Hi Kumar:
> >
> >> Is this for 2.6?=A0
> >
> > 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.=A0 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=20=
> about
> > board_ocp[] in lite5200.c (platform specific). Then yes, I use it,=20=
> but
> > not mpc5200.c
> >
> No, what he said is that MPC5200 needs to be moved to use the =
platform
> bus driver model.
>
> I'll post the patch doing just that on Monday along with PCI and =
sparse
> clean-ups. (Unless something goes wrong ...)
>
>
>
> =A0=A0=A0 Sylvain
next prev parent reply other threads:[~2005-03-09 19:24 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
2005-03-09 18:37 ` Sylvain Munaut
2005-03-09 19:24 ` Kumar Gala [this message]
[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=22bb842e4ff1ada507be76703dda06f9@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=paulus@samba.org \
--cc=tnt@246tNt.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).