From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-74424-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 30846 invoked by alias); 4 Nov 2016 16:10:54 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 30793 invoked by uid 89); 4 Nov 2016 16:10:53 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=annoying, internally, 0x0a, 0x0A
X-HELO: mail-yw0-f169.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:sender:subject:to:references:cc:from:message-id
         :date:user-agent:mime-version:in-reply-to:content-transfer-encoding;
        bh=nXp1rFzQfYoUzsF4juRB/zS9DDXGNkiGdttNVWvCrVM=;
        b=SmoeixZUXJ8P+L0RKL2NL0spvejX4znT1CcZi8n8HfQ57ay4NmBcyUC9SP9LbQrF94
         BFZQianQ2Ry196RRebFam1o4G4HojVASOw31jKWaQeHjep0if9Th8IVYozH8evBRIqtO
         fnDbZJrjcT2NP0WTQ2AUPpH+xxRFrKuZZAnTnbWpJacqHpX0zshHVIOyE9wtJyHKFsHa
         KMZo7JYqAaya/F2aHyQ9i1wSiKzhhTIdJA5815ZfbYe4u6H9PUqLZ62pYe4dmNxdrDCu
         q6bbqXELppI9p+/2ln6+TiH3s2s18M315h3zxmp1PL8uhVYj0q78EJlGRc9oDu5UXPbv
         UUBQ==
X-Gm-Message-State: ABUngveny96msFi5Fc94X9Jl925ZANEeUqC9tCzp1ECWjuX/garmTYeKrYviKHMPJhhU7w==
X-Received: by 10.107.142.2 with SMTP id q2mr5898754iod.128.1478275841555;
        Fri, 04 Nov 2016 09:10:41 -0700 (PDT)
Subject: Re: [RFC][PATCH 0/2] Make sparcv8 work again on cas enabled hardware
To: David Miller <davem@davemloft.net>
References: <1478187561.7146.742.camel@localhost.localdomain>
 <20161103.132213.598669006383889263.davem@davemloft.net>
 <af38a965-24a4-3baf-40e5-7629103a0b1e@twiddle.net>
 <20161104.113100.1070023733565010549.davem@davemloft.net>
Cc: triegel@redhat.com, andreas@gaisler.com, libc-alpha@sourceware.org,
 adhemerval.zanella@linaro.org, carlos@redhat.com, software@gaisler.com
From: Richard Henderson <rth@twiddle.net>
Message-ID: <f56d6520-3a5e-a781-7c4d-bb4b56dc64cf@twiddle.net>
Date: Fri, 04 Nov 2016 16:10:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <20161104.113100.1070023733565010549.davem@davemloft.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2016-11/txt/msg00177.txt.bz2

On 11/04/2016 09:31 AM, David Miller wrote:
> From: Richard Henderson <rth@twiddle.net>
>> The CAS for leon userspace uses ASI_USERDATA (0x0A), not the v9 ASI_P
>> (0x80). It's a really annoying difference that I wish the cpu
>> designers hadn't made.
>
> I don't think they had much choice in the matter given how the ASIs
> are doled out in v9 vs. pre-v9. :-/
>

I didn't think 0x80 was used for anything else on v8, or leon specifically. 
AFAICS it could easily have been made an alias for 0x0A internally.

But oh well, it's done.


r~