From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FREER-0006SK-5Q
	for qemu-devel@nongnu.org; Wed, 05 Apr 2006 16:03:59 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FREEP-0006Ru-4d
	for qemu-devel@nongnu.org; Wed, 05 Apr 2006 16:03:58 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FREEO-0006Rr-VH
	for qemu-devel@nongnu.org; Wed, 05 Apr 2006 16:03:56 -0400
Received: from [212.8.0.13] (helo=rosi.naasa.net)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FREHy-0003Ox-KK
	for qemu-devel@nongnu.org; Wed, 05 Apr 2006 16:07:38 -0400
Received: from jako.ping.de (p50910806.dip0.t-ipconnect.de [80.145.8.6])
	by rosi.naasa.net (Postfix) with ESMTP id AA6C422AEB5
	for <qemu-devel@nongnu.org>; Wed,  5 Apr 2006 22:03:53 +0200 (CEST)
From: Joerg Platte <lists@naasa.net>
Subject: Re: [Qemu-devel] SPARC iommu mapping
Date: Wed, 5 Apr 2006 22:03:50 +0200
References: <BAY104-F2926FE4988EEFCC93C59DFFFCB0@phx.gbl>
In-Reply-To: <BAY104-F2926FE4988EEFCC93C59DFFFCB0@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Disposition: inline
Message-Id: <200604052203.51199.lists@naasa.net>
Content-Transfer-Encoding: quoted-printable
Reply-To: jplatte@naasa.net, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Am Mittwoch, 5. April 2006 19:36 schrieb Blue Swirl:
Hi!

> The DMA controllers for both ESP and Lance are within the same page. Th=
is
> means that in Qemu, DMA controller register accesses for either of them=
 go
> to just one of these. It just happens to work, but maybe this causes th=
e
> problem. You could try to confirm this by enabling also DEBUG_LANCE and=
 see
> if there is troublesome activity in the Lance direction near the bad
> accesses.

Lance is only used during system startup. Then there is no more debugging=
=20
output. Looks like ethernet is not causing any problems.=20

Can you reproduce my problems, or is it caused by the kernel? But the sam=
e=20
kernel works without problems on a SS4...

regards,
J=F6rg