linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Patrick Lerda <Lerda@microprocess.com>
Cc: Nguyen Xuan Hoang <hoang_nguyen@op.com.sg>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: MMU problems?
Date: Thu, 22 Jun 2000 11:58:14 -0400	[thread overview]
Message-ID: <39523796.FF6BFC9F@embeddededge.com> (raw)
In-Reply-To: 17B78BDF120BD411B70100500422FC63079F9D@IIS000


Patrick Lerda wrote:
>
> Have you tried to do complex operation on a 8xx board like compiling the
> kernel.

Yes, and it runs just like any other system that doesn't have any
swap space and a minimal amount of memory.  Some things just don't
work well, and applications fail because few test for memory allocation
failure.

Are there bugs?  Perhaps.  Do I want them fixed?  Yes.

Do you want to help this FREE software effort?  If you are so sure
there is an MMU bug, find it, fix it, and send me the patch.  We would
all be grateful.  If you want dedicated help to assist your custom
product development so you can make money, you may have to pay one
of the very capable embedded Linux companies for this attention.

Thanks.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-06-22 15:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-22  7:01 MMU problems? Patrick Lerda
2000-06-22 15:58 ` Dan Malek [this message]
     [not found] <17B78BDF120BD411B70100500422FC63079FA3@IIS000>
2000-06-25 16:41 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2000-06-23  8:06 Patrick Lerda
2000-06-23  7:43 Patrick Lerda
2000-06-23  8:32 ` Wolfgang Denk
2000-06-22 13:44 Lucinda Schafer
2000-06-22 14:19 ` Daris Nevil
2000-06-22 17:25 ` Wolfgang Denk
1999-12-22  4:02 Nguyen Xuan Hoang
2000-06-22  3:56 ` Dan Malek

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=39523796.FF6BFC9F@embeddededge.com \
    --to=dan@netx4.com \
    --cc=Lerda@microprocess.com \
    --cc=hoang_nguyen@op.com.sg \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).