From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot] GT-64120 PCI init
Date: Tue, 12 Aug 2008 15:02:59 +0900 [thread overview]
Message-ID: <48A12793.9030704@ruby.dti.ne.jp> (raw)
In-Reply-To: <f75c52840808112133v77e3d642xffa7c5ccc1e17531@mail.gmail.com>
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
prev parent reply other threads:[~2008-08-12 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 12:05 [U-Boot-Users] GT-64120 PCI init Richard Danter
2008-08-08 2:31 ` Jerry Van Baren
2008-08-08 2:44 ` [U-Boot] " Jerry Van Baren
2008-08-08 14:39 ` Richard Danter
2008-08-08 14:42 ` [U-Boot] " Richard Danter
2008-08-12 2:20 ` Richard Danter
2008-08-12 4:33 ` Richard Danter
2008-08-12 6:02 ` Shinya Kuribayashi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A12793.9030704@ruby.dti.ne.jp \
--to=skuribay@ruby.dti.ne.jp \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox