public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/8] xtensa: add core information for the dc233c processor
Date: Fri, 15 Jul 2016 02:19:35 +0300	[thread overview]
Message-ID: <20160714231935.GD31001@octofox.metropolis> (raw)
In-Reply-To: <CAPnjgZ2A_yCDbd3awtWW4VS-uQLgj_YUbstn5XzatgB+S=6LpQ@mail.gmail.com>

Hi Simon,

On Tue, Jul 12, 2016 at 03:56:49PM -0600, Simon Glass wrote:
> On 8 July 2016 at 09:42, Max Filippov <jcmvbkbc@gmail.com> wrote:
> > Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> > ---
> 
> Commit message?

Will add.

> >  arch/xtensa/include/asm/arch-dc233c/core.h    | 475 ++++++++++++++++++++++++++
> >  arch/xtensa/include/asm/arch-dc233c/tie-asm.h | 193 +++++++++++
> >  arch/xtensa/include/asm/arch-dc233c/tie.h     | 150 ++++++++
> >  3 files changed, 818 insertions(+)
> >  create mode 100644 arch/xtensa/include/asm/arch-dc233c/core.h
> >  create mode 100644 arch/xtensa/include/asm/arch-dc233c/tie-asm.h
> >  create mode 100644 arch/xtensa/include/asm/arch-dc233c/tie.h
> >
> > diff --git a/arch/xtensa/include/asm/arch-dc233c/core.h b/arch/xtensa/include/asm/arch-dc233c/core.h
> > new file mode 100644
> > index 0000000..3a2e53b
> > --- /dev/null
> > +++ b/arch/xtensa/include/asm/arch-dc233c/core.h
> > @@ -0,0 +1,475 @@
> > +/*
> > + * xtensa/config/core-isa.h -- HAL definitions that are dependent on Xtensa
> > + *                             processor CORE configuration
> > + *
> > + *  See <xtensa/config/core.h>, which includes this file, for more details.
> > + */
> > +
> > +/* Xtensa processor core configuration information.
> > +
> > +   Copyright (c) 1999-2010 Tensilica Inc.
> > +
> > +   Permission is hereby granted, free of charge, to any person obtaining
> > +   a copy of this software and associated documentation files (the
> > +   "Software"), to deal in the Software without restriction, including
> > +   without limitation the rights to use, copy, modify, merge, publish,
> > +   distribute, sublicense, and/or sell copies of the Software, and to
> > +   permit persons to whom the Software is furnished to do so, subject to
> > +   the following conditions:
> > +
> > +   The above copyright notice and this permission notice shall be included
> > +   in all copies or substantial portions of the Software.
> > +
> > +   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> > +   EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> > +   MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
> > +   IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
> > +   CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
> > +   TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
> > +   SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.  */
> 
> */ on next line
> 
> Can you use SPDX for this?

Ok.

> > +
> > +#ifndef _XTENSA_CORE_CONFIGURATION_H
> > +#define _XTENSA_CORE_CONFIGURATION_H
> > +
> > +
> > +/****************************************************************************
> > +           Parameters Useful for Any Code, USER or PRIVILEGED
> > + ****************************************************************************/
> 
> Would be better without all this * and - stuff I think.

Again: autogenerated, not really meant to be edited or even read by
humans. Is it worth it?

-- 
Thanks.
-- Max

  reply	other threads:[~2016-07-14 23:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 15:41 [U-Boot] [PATCH v2 0/8] U-Boot port to Xtensa architecture Max Filippov
2016-07-08 15:41 ` [U-Boot] [PATCH 1/8] xtensa: add support for the xtensa processor architecture [1/2] Max Filippov
2016-07-12 21:56   ` Simon Glass
2016-07-14 21:55     ` Max Filippov
2016-07-08 15:42 ` [U-Boot] [PATCH 2/8] xtensa: add support for the xtensa processor architecture [2/2] Max Filippov
2016-07-12 21:56   ` Simon Glass
2016-07-14 22:58     ` Max Filippov
2016-07-15  0:20       ` Simon Glass
2016-07-08 15:42 ` [U-Boot] [PATCH 3/8] xtensa: add core information for the dc232b processor Max Filippov
2016-07-12 21:56   ` Simon Glass
2016-07-14 23:15     ` Max Filippov
2016-07-15  0:20       ` Simon Glass
2016-07-08 15:42 ` [U-Boot] [PATCH 4/8] xtensa: add core information for the dc233c processor Max Filippov
2016-07-12 21:56   ` Simon Glass
2016-07-14 23:19     ` Max Filippov [this message]
2016-07-08 15:42 ` [U-Boot] [PATCH 5/8] xtensa: add core information for the de212 processor Max Filippov
2016-07-12 21:56   ` Simon Glass
2016-07-14 23:20     ` Max Filippov
2016-07-08 15:42 ` [U-Boot] [PATCH 6/8] net/ethoc: support private memory configurations Max Filippov
2016-07-12 21:56   ` Simon Glass
2016-07-14 23:34     ` Max Filippov
2016-07-15  0:20       ` Simon Glass
2016-07-08 15:42 ` [U-Boot] [PATCH 7/8] net/ethoc: don't advertise gigabit on the connected PHY Max Filippov
2016-07-12 21:56   ` Simon Glass
2016-07-14 23:41     ` Max Filippov
2016-07-13  6:28   ` Michal Simek
2016-07-14 23:51     ` Max Filippov
2016-07-08 15:42 ` [U-Boot] [PATCH 8/8] xtensa: add support for the 'xtfpga' evaluation board Max Filippov
2016-07-12 21:57   ` Simon Glass
2016-07-15  0:13     ` Max Filippov
2016-07-13  6:35   ` Michal Simek
2016-07-15  0:04     ` Max Filippov

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=20160714231935.GD31001@octofox.metropolis \
    --to=jcmvbkbc@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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