From owner-freebsd-arm@FreeBSD.ORG  Wed Mar  6 12:43:35 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id A52CE1A8
 for <freebsd-arm@freebsd.org>; Wed,  6 Mar 2013 12:43:35 +0000 (UTC)
 (envelope-from aoyama@peach.ne.jp)
Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98])
 by mx1.freebsd.org (Postfix) with ESMTP id 61A4588F
 for <freebsd-arm@freebsd.org>; Wed,  6 Mar 2013 12:43:35 +0000 (UTC)
Received: from moon.peach.ne.jp (localhost [127.0.0.1])
 by moon.peach.ne.jp (Postfix) with ESMTP id 9FC1639E09;
 Wed,  6 Mar 2013 21:43:27 +0900 (JST)
Received: from artemis (unknown [172.18.0.20])
 (using TLSv1 with cipher AES128-SHA (128/128 bits))
 (No client certificate requested)
 by moon.peach.ne.jp (Postfix) with ESMTPSA id 893B039D62;
 Wed,  6 Mar 2013 21:43:27 +0900 (JST)
Message-ID: <DCFED2B21AAB4EC19FF4358CEEAB1C3A@ad.peach.ne.jp>
From: "Daisuke Aoyama" <aoyama@peach.ne.jp>
To: "Oleksandr Tymoshenko" <gonzo@bluezbox.com>
References: <B5F827FF91C94FF2AFEE00194A2BB2C5@ad.peach.ne.jp>
 <B508111FCE534B2CBA61F4D1EC1078D3@ad.peach.ne.jp>
 <D3ABE3919EA74D668DB060952B5CD8C0@ad.peach.ne.jp>
 <2659960079254C38ACD2F1DCBB7A1A19@ad.peach.ne.jp>
 <E48DEAF481F74C69A1BC7A01F2B8E74A@ad.peach.ne.jp>
 <D867259F89CF44409C2359527D0263D4@ad.peach.ne.jp>
 <512FD3E8.4000307@bluezbox.com>
 <2D2EAE5B346840A49A5D99A9BFD1DA1D@ad.peach.ne.jp> <51364F20.500@bluezbox.com>
In-Reply-To: <51364F20.500@bluezbox.com>
Subject: Re: FreeBSD/armv6z/clang on Raspberry Pi 512MB (with U-Boot + ubldr)
Date: Wed, 6 Mar 2013 21:43:28 +0900
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="ISO-8859-1";
 reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8117.416
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: freebsd-arm@freebsd.org
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 12:43:35 -0000

> These are not really required. With current code if dreq is zero it will
> overwrite info bits properly while when patched - bits will be left untouched
> from previous setup call.

No, you need it. Current code cannot handle PERMAP (not INFO_S_DREQ and INFO_D_DREQ) if calling 
it with:

setup_src(IO/DREQ_XXXX) *1
setup_dst(mem/DREQ_NONE)

or

setup_dst(IO/DREQ_XXXX) *2
setup_src(mem/DREQ_NONE)

Note: Peripheral Mapping(20:16, see p.51) is shared by both src and dst.
At least, you cannot use like:

> info &= ~INFO_PERMAP_MASK;

Because, previous call (*1 and *2) may put a value to it.

-- 
Daisuke Aoyama