Received: by 10.223.164.202 with SMTP id h10csp1231wrb; Thu, 9 Nov 2017 01:34:48 -0800 (PST) X-Google-Smtp-Source: ABhQp+Qq9eqTQM1A35W7H69StrCAm3D8N5A8bJAV27+XK7XEuqnKStT6wxooYbGrrIyNS1D+oCCb X-Received: by 10.101.93.77 with SMTP id e13mr3301346pgt.431.1510220088222; Thu, 09 Nov 2017 01:34:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510220088; cv=none; d=google.com; s=arc-20160816; b=Ua92BXsEYkI905TvzaZJby8nkKNJFpTXSCpBxC/NHFt9ESoSovCdKZFi/d1uvPUskI i2S0ivI2TzC9SGfp2I9VsR2IgnGTKh7UBjU7+PYiX0wn1dhpykk0fnxnOwZajTJMdECH rdBtij4PJmD3I5TkrOSiszyrpvRnEXdtqIiGmznJX/kmmYUtPIXWwK8bPUqtwcwQspIs 1mKlK42/dnRP7BJctRIjKVTrXgXrPl7QstZMDtnazTn4je69KFSFQ+dgRgle2PYu5ufY 0OXvhGyrj1F7pbcG1neBG/23VzgpVkavky8HZxPfplAfde6/SPWTsL2/RNqKQVT8Uo+N 433w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=vQGq3iQ8ypPpjeSh7on5DdGzVira267bDuZ7c/y7vE4=; b=rJvJ7xzxNeRHtJs7/5/WyM2TfmfSjMRu3JbBNOcBnWD8+RXFd2cQNROUFn+Ortj82Q X6d8MNp3xVjWFmF75ppkvNx2SV1HPKh2Im7+O1k5joYjET03KeQoVHQJIGQXbjr0yMJE sr8klQdRriG/uV6U7U/6ytS1QSuLdGHqEGFtx6te7ktZwPUU52XkcnCfLqow9xOTRp7Z cVLQ/gm6Hyfc83O74FmurH6bgtvi4Dsk6JIsIv2FqJwwtub3Aqo2dZJHqApQ6+FJmdsu 5WN0oiFGe6mfucwAPd+lVqE2bQEjo5NB4SKWghPTTGBExJ0hoIf0WG25TlSY/7ZvYyKG dWYw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=FrVK2q2S; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b5si5631503pgc.137.2017.11.09.01.34.36; Thu, 09 Nov 2017 01:34:48 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=FrVK2q2S; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753640AbdKIJd6 (ORCPT + 82 others); Thu, 9 Nov 2017 04:33:58 -0500 Received: from mail-vk0-f68.google.com ([209.85.213.68]:55850 "EHLO mail-vk0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752675AbdKIJdy (ORCPT ); Thu, 9 Nov 2017 04:33:54 -0500 Received: by mail-vk0-f68.google.com with SMTP id b7so3530014vkh.12; Thu, 09 Nov 2017 01:33:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vQGq3iQ8ypPpjeSh7on5DdGzVira267bDuZ7c/y7vE4=; b=FrVK2q2Sa0ih5YaaY2vZqGpJQQZGDsZUGo9fIr6Qd6dPaQxY7ez6fnl9RjtlaF+xSR G78NlGW2CrQeKF68JfcYfGk18K5tTGyUYOt8eFa35CaTkTWWmTBGzHK68LjPmlwO8aeF w4dQ8l/RJig6ZkoW4Cu3VoOlBOo2SVIVQR0rLFF/kb8vqlHRSCl5mdNfr9n1XIoRjT7F kpSkyn8NC3wOeZOaxp2fw+QHcaXjz1FeJWEsMysCKzx6xQZWdPkdfnSSr4/3p7X759ML s8SHEr4haZ8eIMWimsc9Kdi/lS5DYGUqBkQ25Uure+ujU4whqvQsrV/GFReJqEmZHJU8 7xRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vQGq3iQ8ypPpjeSh7on5DdGzVira267bDuZ7c/y7vE4=; b=t0/Db1M/mPhHybr7w5c1+pe3scdf9bCt4ZKmj0nyEHZtVA71rPN5UR6MW38mHCUmzw LtmZxP6ITf3WWmuVRIFgTWAuS1BeVQNGlFlRkst81C0FZYg2fyfzvXioR4TF56Oq5r40 6M2m8gzP6rlvDkOVYZgaMkufnpNPW/a8ORALUGW9MCji+X706XpHWlCrtAVBjOzuSxUp GdWYNUajPRa+RfNCqK1YXRtR7zUePMHBOnTJuNHp+zlzRn7TIh5XHDBFoK7aECenEKcj MBRwCq2rh678AYGnGhYJmTCyNijn+a1utfv/2uk6uI2Xdr7QzxquYUh4ro7i/vUxsE7J aFeA== X-Gm-Message-State: AJaThX4wNL+uBMx8txWx1eTcBsA1ZgTyOClD7cN/GD8HmvoPf3snfoix spUaeZQMrg6rNm2QNrjGqBpgamygTBlqONa2vqk= X-Received: by 10.31.51.76 with SMTP id z73mr2649888vkz.192.1510220033620; Thu, 09 Nov 2017 01:33:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.62.8 with HTTP; Thu, 9 Nov 2017 01:33:13 -0800 (PST) In-Reply-To: References: From: Greentime Hu Date: Thu, 9 Nov 2017 17:33:13 +0800 Message-ID: Subject: Re: [PATCH 00/31] Andes(nds32) Linux Kernel Port To: Arnd Bergmann Cc: Greentime , Linux Kernel Mailing List , linux-arch , Thomas Gleixner , Jason Cooper , Marc Zyngier , Rob Herring , Networking Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2017-11-08 18:26 GMT+08:00 Arnd Bergmann : > On Wed, Nov 8, 2017 at 6:54 AM, Greentime Hu wrote: >> This patchset adds core architecture support to Linux for Andestech's >> N13, N15, D15, N10, D10 processor cores. >> >> Based on the 16/32-bit AndeStar RISC-like architecture, we designed the >> configurable AndesCore series of embedded processor families. AndesCores >> range from highly performance-efficient small-footprint cores for >> microcontrollers and deeply-embedded applications to 1GHz+ cores running >> Linux, covering general-purpose N-series cores for a wide range of computing >> need, DSP-capable D-series cores for digital signal control, >> instruction-extensible E-series cores for application-specific acceleration, >> and secure S-series cores for best protection of the most valuable. > > I looked at the entire patch series now and commented on anything I noticed > that could be improved, overall this looks very nice, great work! > > Most of my comments are about tiny details that are easy to address. > > I see two areas that need to be looked at carefully, and that may take a > few more rounds to get right: > > - In the user space ABI, you have a couple of things that differ from the > normal asm-generic definitions, i.e. s few syscall entry points and some > types in asm/posix-types.h. I guess you did that to remain compatible > with an older glibc port, but IMHO this compatibility should be broken > in favor of having the standard ABI before the port gets merged. > > - For the boot interface, you need to clearly define what can be expected > and what cannot. This involves the presence of the l2cc, the physical > memory address, the built-in dtb, and probably a few more things I > missed. For long-term maintainability, you probably want to ensure that > you can build a kernel that runs on as much diverse hardware as possible. > Many thanks to all your feedbacks. We will prepare the V2 patch to fix them ASAP. :) From 1583580120723619216@xxx Thu Nov 09 09:28:09 +0000 2017 X-GM-THRID: 1583483388365849169 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread