linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Tobias Otto-Adamczak <Tobias.Otto-Adamczak@e-technik.tu-chemnitz.de>
Cc: Julia Elbert <jelbert@enerdyne.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: no scc_hdlc struct in commproc.h
Date: Wed, 13 Sep 2000 12:26:27 -0400	[thread overview]
Message-ID: <39BFAAB3.E6993D3@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.21.0009131118150.24289-100000@odoaker.hrz.tu-chemnitz.de


Tobias Otto-Adamczak wrote:

> /*********   SCC parameter RAM for HDLC mode   *********/

Just a couple of minor comments......

> typedef struct scc_hdlc {

>         ushort  scc_rbase;      // Rx Buffer descriptor base address
>         ushort  scc_tbase;      // Tx Buffer descriptor base address
>         u_char  scc_rfcr;       // Rx function code
>         u_char  scc_tfcr;       // Tx function code
>         ushort  scc_mrblr;      // Max receive buffer length
>         uint    scc_rstate;     // internal
>         uint    scc_idp;        // internal
>         ushort  scc_rbptr;      // internal
>         ushort  scc_ibc;        // internal
>         uint    scc_rxtmp;      // internal
>         uint    scc_tstate;     // internal
>         uint    scc_tdp;        // internal
>         ushort  scc_tbptr;      // internal
>         ushort  scc_tbc;        // internal
>         uint    scc_txtmp;      // internal
>         uint    scc_rcrc;       // internal
>         uint    scc_tcrc;       // internal

This first part of the object is defined by 'scc_param', so the
convention would have been:

typedef struct scc_hdlc {
	sccp_t	scc_hdlc;

Followed by:
>         // here begins HDLC specific part
>         uint    scc_res1;       // reserved

The documentation describes the CPM devices in this way, and it is
a little more clear what is common to the SCC, and what is unique
to the HDLC feature.

....since we aren't writing C++, I also dislike the '//' comment......

I would have made these two changes if it was sent as a patch to
me for inclusion in the source code.....

In fact, I will keep this and include it in the future....Do you have
any code you want to submit along with it?



	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-09-13 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-12 20:11 no scc_hdlc struct in commproc.h Julia Elbert
2000-09-13  2:21 ` Dan Malek
2000-09-13  9:21 ` Tobias Otto-Adamczak
2000-09-13 16:26   ` Dan Malek [this message]

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=39BFAAB3.E6993D3@mvista.com \
    --to=dan@mvista.com \
    --cc=Tobias.Otto-Adamczak@e-technik.tu-chemnitz.de \
    --cc=jelbert@enerdyne.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).