All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: [RFC] PlatformDevice definitions for 82xx
Date: Fri, 3 Jun 2005 01:13:02 -0500	[thread overview]
Message-ID: <81bbf71b42314c9168681be6ef2725e1@freescale.com> (raw)
In-Reply-To: <429F30D7.2040806@ru.mvista.com>


On Jun 2, 2005, at 11:16 AM, Vitaly Bordug wrote:

> Hi!
> This adds platform definition files for 82xx, while the platform_info 
> is
> filled in board-specific .C file residing in platforms/82xx. Another
> disputable thing I did - I moved m8260_setup.c from the syslib/ up to
> platforms/82xx/. The file was slightly changed  - added 2 prototypes
> from the cpm2_pic.h and removed the respective include.

Why the move of m8260_setup.c?  Also, if this is required can we do 
this as two different patches so we can see clearly any changes also 
maded to m8260_setup.c

mpc82xx_devices.c need a bit of work we need to at least cover the same 
set of devices that 85xx does for the CPM:
	SPI, I2C, USB, SCC1-4, FCC1-3, MCC1-2, SMC1-2

Additionally, the device name can not me FS_ENET_NAME, which assumes 
that FCC is only used for enet.

mpc82xx_sys.c: what is the .value field?  is this the IMMR and if so 
why bother shifting it?  Also there are a whole bunch of variants that 
need to be captured

Let's get clean versions of these two files before we worry about how 
to handle FCC enet specific bits.

- kumar

  reply	other threads:[~2005-06-03  6:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 16:16 [RFC] PlatformDevice definitions for 82xx Vitaly Bordug
2005-06-03  6:13 ` Kumar Gala [this message]
2005-06-03 15:21   ` Vitaly Bordug
2005-06-03 15:26     ` Kumar Gala

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=81bbf71b42314c9168681be6ef2725e1@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=vbordug@ru.mvista.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 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.