Date: Thu, 26 Mar 2015 09:11:54 +0200 From: "moskova rehber" <bilgilendirme71@mail.ru> To: freebsd-arm@freebsd.org Subject: MOSKOVA..... Message-ID: <FDC0440B4F7BC0AB78DA8A2F6E9AC344B1E16785@MOSKOVA>
next in thread | raw e-mail | index | archive | help
=20
www.moskovadarehber.com
TEL: +7 965 229 78 50
info@moskovadarehber.com
Havaliman=C4=B1 kar=C5=9F=C4=B1lama ve transfer: Belki yurtd=C4=B1=C5=9F=C4=
=B1na ilk defa =C3=A7=C4=B1k=C4=B1yorsunuz, belki de inece=C4=9Finiz =C5=9F=
ehri hi=C3=A7 bilmiyor ve =C5=9Fehir merkezine nas=C4=B1l giderim diye d=C3=
=BC=C5=9F=C3=BCn=C3=BCyorsunuz. Bu gibi durumlarda sizi havaliman=C4=B1nda =
kar=C5=9F=C4=B1l=C4=B1yor ve birlikte kalaca=C4=9F=C4=B1n=C4=B1z otele kada=
r giderek check-in i=C5=9Flemlerinizi yap=C4=B1yoruz. =20
Rehberik ve Terc=C3=BCmanl=C4=B1k: Terc=C3=BCmanl=C4=B1k =E2=80=93 Teknik T=
erc=C3=BCmanl=C4=B1k =E2=80=93 Simultane Terc=C3=BCmanl=C4=B1k =E2=80=93 Fu=
ar ve i=C5=9F g=C3=B6r=C3=BC=C5=9Fmelerinde terc=C3=BCmanl=C4=B1k =
=20
=C5=9Eehir ve tur rehberi: Turistik ama=C3=A7l=C4=B1 olarak Moskovaya=E2=80=
=99ya geldiyseniz ya da i=C5=9F gezinizden f=C4=B1rsat buldu=C4=9Funuz bir =
anda =C5=9Fehri gezmek isterseniz Moskova'n=C4=B1n gezilmesi ve g=C3=B6r=
=C3=BClmesi gereken yerlerini gezdiriyor veya k=C4=B1sa bir Panoramik Mosko=
va =C5=9Fehir turu (ara=C3=A7l=C4=B1) yap=C4=B1yoruz.
Otel veya g=C3=BCnl=C3=BCk kiral=C4=B1k ev rezervasyonu: =C4=B0stedi=C4=9Fi=
niz =C3=B6zellikler dikkate al=C4=B1narak, ula=C5=9F=C4=B1m ve b=C3=BCt=C3=
=A7e a=C3=A7=C4=B1s=C4=B1ndan en uygun oteli veya evi bularak rezervasyon i=
=C5=9Flemlerini yap=C4=B1yoruz.
Ticari toplant=C4=B1larda terc=C3=BCmanl=C4=B1k: Moskova=E2=80=99ya bir i=
=C5=9F g=C3=B6r=C3=BC=C5=9Fmesi i=C3=A7in geldiniz, pazarl=C4=B1k yap=C4=B1=
lacak, kontrat imzalanacak ya da sadece g=C3=B6r=C3=BC=C5=9Fme yap=C4=B1lac=
ak. Bu gibi durumlarda yan=C4=B1n=C4=B1zda bulunuyor ve kar=C5=9F=C4=B1 tar=
af ile sorunsuzca anla=C5=9Fman=C4=B1z=C4=B1 sa=C4=9Fl=C4=B1yoruz
=C4=B0=C5=9F takibi: =C4=B0htiyac=C4=B1n=C4=B1z do=C4=9Frultusunda herhangi=
bir konudaki i=C5=9F takibi ihtiyac=C4=B1n=C4=B1z=C4=B1 kar=C5=9F=C4=B1l=
=C4=B1yoruz. =C3=96rne=C4=9Fin istedi=C4=9Finiz bir =C3=BCr=C3=BCn=C3=BC bu=
larak T=C3=BCrkiye=E2=80=99deki adresinize yolluyoruz ya da bir =C5=9Firket=
le, ki=C5=9Fiyle g=C3=B6r=C3=BC=C5=9Fmeniz gerekiyorsa sizin i=C3=A7in topl=
ant=C4=B1ya giriyor, pazarl=C4=B1k yap=C4=B1yor ve g=C3=B6r=C3=BC=C5=9Fmeyi=
ger=C3=A7ekle=C5=9Ftiriyoruz.
Evrak terc=C3=BCmesi: Her t=C3=BCrl=C3=BC evraklar=C4=B1n=C4=B1z=C4=B1n (re=
smi ve resmi olmayan) noter onayl=C4=B1 terc=C3=BCmesi =C3=A7ok k=C4=B1sa b=
ir s=C3=BCrede, g=C3=BCvenilir bir =C5=9Fekilde yap=C4=B1l=C4=B1r ve gerekl=
i yerlere teslimat=C4=B1 yap=C4=B1l=C4=B1r.
Taksi ve transfer: Moskovada g=C3=BCn=C3=BCn her saatinde size hizmet edebi=
lecek iyi derecede rus=C3=A7a konu=C5=9Fabilen t=C3=BCrk taksi.
www.moskovadarehber.com
TEL: +7 965 229 78 50
info@moskovadarehber.com
From owner-freebsd-arm@FreeBSD.ORG Sun Mar 29 19:05:51 2015
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])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 0A3A952A
for <freebsd-arm@FreeBSD.org>; Sun, 29 Mar 2015 19:05:51 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
[IPv6:2001:1900:2254:206a::16:76])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id E1BEEA2F
for <freebsd-arm@FreeBSD.org>; Sun, 29 Mar 2015 19:05:50 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2TJ5oIx032063
for <freebsd-arm@FreeBSD.org>; Sun, 29 Mar 2015 19:05:50 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-arm@FreeBSD.org
Subject: [Bug 196081] [PATCH] ARM: sunxi: Add driver for the MMC/SD host
found in the Allwinner A10 SoC
Date: Sun, 29 Mar 2015 19:05:49 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: arm
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords:
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: omgalvan.86@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-196081-7-L5odCdCRWq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-196081-7@https.bugs.freebsd.org/bugzilla/>
References: <bug-196081-7@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <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: Sun, 29 Mar 2015 19:05:51 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196081
--- Comment #7 from Martin Galvan <omgalvan.86@gmail.com> ---
(In reply to Pratik Singhal from comment #6)
I looked at the patch you sent. Did you actually test this on the
board with CURRENT? The reason I'm asking is that I don't think that
patch could work as intended.
You're doing:
do {
reg_value = a10_mmc_read_4(sc, A10_MMC_GLOBAL_CONTROL_REG);
} while ((!reg_value & A10_MMC_HARDWARE_RESET_BITS) && (--time_left));
Do you realize the ! is zeroing reg_value before it gets AND-ed with
A10_MMC_HARDWARE_RESET_BITS? I think what you wanted to do was:
!(reg_value & A10_MMC_HARDWARE_RESET_BITS)
Now, I don't remember every detail of how the host worked, but I
recall I had to wait while the hardware reset bits were set on the
global control reg; it would be safe to proceed only after those bits
were cleared. I think the hardware automatically clears those bits
after the reset is finished. I may be wrong, though.
The problem Bas reported sounds to me like a NULL pointer being
dereferenced somewhere, or something like that. I think that may be
the cause because we'd always get a translation fault when doing
something like that, while waiting forever would usually just cause
the system to hang.
--
You are receiving this mail because:
You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FDC0440B4F7BC0AB78DA8A2F6E9AC344B1E16785>