All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr G Zhadan <oleks@arcturusnetworks.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Arcturus uCP1020 BSP support.
Date: Thu, 7 Jul 2016 12:32:55 -0400	[thread overview]
Message-ID: <577E8437.80801@arcturusnetworks.com> (raw)
In-Reply-To: <20160707153745.GD20199@waldemar-brodkorb.de>

Hi Waldemar,

Nothing wrong with the default one in this basic BSP support I sent to you.
Our local stuff is more complicated and has some extra patches to the 
uClibc-ng.config and that's what for we have to have the 
separate Arcturus specific uClibc-ng.config and theoretically it could 
be removed.
Please let me know if I have to do it and I will send second version 
without .../arcturus/ppc-ucp1020/configs/uClibc-ng.config.

Any other issues you noticed ?

Thank you,

Oleksandr


On 07/07/2016 11:37 AM, Waldemar Brodkorb wrote:
> HI Oleksandr,
> Oleksandr G Zhadan wrote,
>
>> The uCP1020 product family (ucp1020) is an Arcturus Networks Inc.
>> System on Modules product featuring a Freescale P1020 CPU,
>> optionally populated with 1 or 2 Gig-Ethernet PHYs,
>> DDR3, NOR Flash, eMMC NAND Flash and/or SPI Flash.
>>
>> Signed-off-by: Oleksandr Zhadan <arcsupport@arcturusnetworks.com>
>> Signed-off-by: Michael Durrant <arcsupport@arcturusnetworks.com>
>> ---
>>   .../ppc-ucp1020/configs/linux-4.1.x.config         | 2911 ++++++++++++++++++
>>   .../arcturus/ppc-ucp1020/configs/uClibc-ng.config  |  243 ++
> Is there a special need to add a separate uClibc-ng config?
> What is wrong in the default one?
>
> best regards
>   Waldemar
>
>


-- 
Oleksandr Zhadan
Arcturus Networks
T 416 621-0125 x235
F 416 621-0190

  reply	other threads:[~2016-07-07 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 14:00 [Buildroot] [PATCH 1/1] Arcturus uCP1020 BSP support Oleksandr G Zhadan
2016-07-07 15:37 ` Waldemar Brodkorb
2016-07-07 16:32   ` Oleksandr G Zhadan [this message]
2016-07-07 20:06 ` Thomas Petazzoni
2016-07-07 21:01   ` Oleksandr G Zhadan
2016-07-07 21:03     ` Thomas Petazzoni

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=577E8437.80801@arcturusnetworks.com \
    --to=oleks@arcturusnetworks.com \
    --cc=buildroot@busybox.net \
    /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.