From: Kumar Gala <kumar.gala@freescale.com>
To: "Jason McMullan" <jason.mcmullan@gmail.com>
Cc: "Gala Kumar K.-galak" <galak@freescale.com>,
linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: RFC: cpm2_devices.c
Date: Wed, 15 Jun 2005 10:01:15 -0500 [thread overview]
Message-ID: <d59e33ec0e627627e2e594075d139b35@freescale.com> (raw)
In-Reply-To: <1118846034.7564.113.camel@jmcmullan.timesys>
On Jun 15, 2005, at 9:33 AM, Jason McMullan wrote:
> On Wed, 2005-06-15 at 09:25 -0500, Kumar Gala wrote:
>> Yes, I removed the fcc_regs_c since its not always true. Please don't
>> rename the file to cpm2_. I think I'm going to end up renaming them
>> to
>> pq2_ since that is the most appropriate name. I'd say we are about
>> 80%
>
> PQ2_? But all these devices are on PQ3 also!
Sure and they are in the mpc85xx_* files. Maybe I'm missing some
concern people have here. It dont see what the issue is. This is just
like how TSEC/gianfar show up in both mpc85xx_* and mpc83xx_*. These
files are intended to represent the devices found on a product family
(PQ2, PQ3, PQ2 Pro, etc.). There is going to be overlap.
Also, its not 100% true that all of the devices on a PQ2 exist in PQ3.
For example (and this isn't a great one) the security block on
8248/8272 is different than the security block on PQ3 devices.
- kumar
next prev parent reply other threads:[~2005-06-15 15:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 18:18 RFC: cpm2_devices.c Allen Curtis
2005-06-15 3:35 ` Kumar Gala
2005-06-15 3:57 ` Allen Curtis
2005-06-15 4:13 ` Kumar Gala
2005-06-15 4:41 ` Allen Curtis
2005-06-15 14:24 ` Jason McMullan
2005-06-15 15:06 ` Kumar Gala
2005-06-15 17:48 ` Allen Curtis
2005-06-15 18:05 ` Vitaly Bordug
2005-06-15 14:29 ` Kumar Gala
2005-06-15 14:30 ` Kumar Gala
2005-06-16 15:12 ` Dan Malek
2005-06-16 15:33 ` Kumar Gala
2005-06-16 15:42 ` Allen Curtis
2005-06-16 15:53 ` Kumar Gala
2005-06-16 16:39 ` Allen Curtis
2005-06-16 19:33 ` Dan Malek
2005-06-15 7:55 ` Vitaly Bordug
2005-06-15 14:25 ` Kumar Gala
2005-06-15 14:33 ` Jason McMullan
2005-06-15 15:01 ` Kumar Gala [this message]
2005-06-15 15:31 ` Vitaly Bordug
2005-06-15 15:41 ` Kumar Gala
2005-06-15 16:07 ` Vitaly Bordug
2005-06-16 6:42 ` Pantelis Antoniou
2005-06-16 9:33 ` Wolfgang Denk
2005-06-16 15:02 ` 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=d59e33ec0e627627e2e594075d139b35@freescale.com \
--to=kumar.gala@freescale.com \
--cc=galak@freescale.com \
--cc=jason.mcmullan@gmail.com \
--cc=linuxppc-embedded@ozlabs.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 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).