All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [arm] Where to put files for armv8 ThunderX
Date: Tue, 21 Jun 2016 07:12:40 +0200	[thread overview]
Message-ID: <5768CCC8.5050508@denx.de> (raw)
In-Reply-To: <602ec2cb-087b-d23d-0771-6b4a2f8ff6ee@caviumnetworks.com>

Hi Aaron,

On 21.06.2016 00:15, Aaron Williams wrote:
> I have just been handed the task of cleaning up our U-Boot port to our
> ThunderX armv8 chip and am wondering where I should put the files
> specific to our chip.
>
> The people who previously worked on the chip created a subdirectory
> under u-boot and have things scattered about.
>
> Should I create a subdirectory under arch/arm/cpu/armv8 like
> arch/arm/cpu/armv8/mach-thunderx or should I create a mach-thunderx
> directory directly under the cpu directory?

I personally prefer mach-thunderx over cpu/xxx/xxx. This is the newer
"directory style" at least for armv7 or earlier platforms. With less
directory levels to type.

> I'm assuming include files should go under
> arch/arm/include/asm/arch-thunderx.

Or arch/arm/mach-thunderx/include/asm.

> I very much want to get this stuff pushed upstream so I don't run into
> the situation we've been stuck with our Octeon MIPS processors.  My
> biggest problem is that a lot of code doesn't work.
>
> I'm still trying to get up to speed with the armv8 U-Boot.

There should be many people on the list being able to assist with
armv8 related questions.

Thanks,
Stefan

  reply	other threads:[~2016-06-21  5:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 22:15 [U-Boot] [arm] Where to put files for armv8 ThunderX Aaron Williams
2016-06-21  5:12 ` Stefan Roese [this message]
2016-09-14 16:14 ` Tim Harvey

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=5768CCC8.5050508@denx.de \
    --to=sr@denx.de \
    --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 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.