From: Jiri Gaisler <jiri@gaisler.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Clean kernel patch for LEON/SPARC
Date: Wed, 20 Aug 2003 19:31:13 +0200 [thread overview]
Message-ID: <3F43B061.3010805@gaisler.com> (raw)
In-Reply-To: <20030820123311.A6511@devserv.devel.redhat.com>
Pete Zaitcev wrote:
> The serial has to go to Russell King, but I can look, too.
> Best of all is to cc to linux-kernel.
>
> About Ethernet, it probably ought to go to netdev@oss.sgi.com.
> I am not quite sure.
>
I have made three patches that makes up the leon/sparc port
for linux-2.5.75:
* linux-2.5.75_kernel_only.diff - leon support in kernel
* linux-2.5.75_open_eth.diff - opencores ethernet driver
* linux-2.5.75_leon_uart.diff - leon uart driver
The total size is about 150 Kbyte, so to avoid a large email
the patches can be downloaded from:
http://www.gaisler.com/patches.html
I don't have Russell King's email address, maybe you could
forward this mail to him?
> Did you guys figure out the cause of the severe problem
> with cache corruption?
Yes, this was a virtual address aliasing problem. Leon2 has
virtual caches but the MMU has no aliasing detection, so we
are forced to flush the cache on each task switch. Our next
processor (leon3) will have to switch to either physical caches
or have some form of aliasing detection ...
Regards, Jiri.
--
-------------------------------------------------------------------------
Gaisler Research, Stora Nygatan 13, 41108 Goteborg, Sweden, +46-31802405
fax: +46-31802407 email: info@gaisler.com, home page: www.gaisler.com
-------------------------------------------------------------------------
parent reply other threads:[~2003-08-20 17:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030820123311.A6511@devserv.devel.redhat.com>]
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=3F43B061.3010805@gaisler.com \
--to=jiri@gaisler.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=zaitcev@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).