From: Kumar Gala <galak@kernel.crashing.org>
To: Jimi Xenidis <jimix@pobox.com>
Cc: Linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: union/struct representations for MAS Registers
Date: Wed, 10 Aug 2011 12:25:14 -0500 [thread overview]
Message-ID: <9FE83BDE-592D-42FC-B2B4-A2B6E7E49206@kernel.crashing.org> (raw)
In-Reply-To: <B952E5AF-98EF-46CE-B30F-7E1EA55C33AC@pobox.com>
On Aug 10, 2011, at 12:21 PM, Jimi Xenidis wrote:
> I have some and use them in some code, they represent ISA 2.06 MAVN=3D1 =
(version 2)
> Can I keep them?
> if so, should I put them somewhere useful to others?
>=20
> Examples:
> union mas1 {
> u32 _val;
> struct {
> u32 v:1;
> u32 iprot:1;
> u32 tid:14;
> u32 _reserved_1:2;
> u32 ind:1;
> u32 ts:1;
> u32 tsize:4;
> u32 _reserved_2:8;
> };
> };
Uugh, we really have avoided unions for such things and it would be nice =
to keep it that way.
- k=
next prev parent reply other threads:[~2011-08-10 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 17:21 union/struct representations for MAS Registers Jimi Xenidis
2011-08-10 17:25 ` Kumar Gala [this message]
2011-08-10 17:31 ` Jimi Xenidis
2011-08-10 17:25 ` David Laight
2011-08-10 17:31 ` Jimi Xenidis
2011-08-10 17:38 ` David Laight
2011-08-10 17:48 ` 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=9FE83BDE-592D-42FC-B2B4-A2B6E7E49206@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=jimix@pobox.com \
--cc=linuxppc-dev@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