From mboxrd@z Thu Jan  1 00:00:00 1970
From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
Date: Tue, 12 Aug 2008 15:02:59 +0900
Subject: [U-Boot] GT-64120 PCI init
In-Reply-To: <f75c52840808112133v77e3d642xffa7c5ccc1e17531@mail.gmail.com>
References: <f75c52840808070505p238b2540o7d8aebf3bef06efc@mail.gmail.com>	<f75c52840808080739x6db787ccl5c9d0af08b2401e@mail.gmail.com>	<f75c52840808080742q7f181ce3m95799a9778cfab70@mail.gmail.com>	<f75c52840808111920l2e5138fcmcb882c8bc5bff154@mail.gmail.com>
	<f75c52840808112133v77e3d642xffa7c5ccc1e17531@mail.gmail.com>
Message-ID: <48A12793.9030704@ruby.dti.ne.jp>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Richard Danter wrote:
> Solution so far is either to run U-Boot from KSeg1 or to pepper the
> eepro100 driver with flush_cache() calls. Both seem to work though
> running in kseg1 is slower.
> 
> Has anyone else used an eepro100 on a MIPS target? Did you hit the same problem?
> 
> I can see that some drivers (e.g. rtl8139.c) already have the
> flush_cache() calls.

I added flush_cache()s to rtl8139.c before.

If your system is cache non-coherent, please fix drivers to have proper
cache handlings. Also note that running whole U-Boot in CKSEG1 is not
good idea, at least for me.

  Shinya