All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Stephen Williams <612dlag102@sneakemail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Hardware Requrements for Linux on 405GPr
Date: Thu, 14 Aug 2003 15:17:13 -0500	[thread overview]
Message-ID: <3F3BEE49.4050806@mvista.com> (raw)
In-Reply-To: <21518-79162@sneakemail.com>


An RTC is not required for Linux.  Many designs I have seen do not have
one.  However, an RTC is an excellent device to have available!  Various
applications and services may require a consistant, ever increasing
time.  NFS is the one that comes to mind immediatly.  If the device is
rebooted and the time goes back to default, NFS may have problems.

RAM is something else thats nice to have.. :)  While 16 MB is usable, 32
MB or more is preferred in the applications that I am used to.  (You can
get away with 8 MB, but thats very tight usually.)

--Mark

Stephen Williams wrote:
>
> We are in the process of designing a PCI board that will have
> a 405GPr, some SDRAM and a Compact Flash. (Not to mention
> the functionality of our device.) Outside the 405GPr itself,
> are there any minimum device requirements for a Linux that
> can for example run some simple servers?
>
> For example, the matter of whether or not a RTC is required
> came up amongst the designers.
> --
> Steve Williams                "The woods are lovely, dark and deep.
> steve at icarus.com           But I have promises to keep,
> http://www.icarus.com         and lines to code before I sleep,
> http://www.picturel.com       And lines to code before I sleep."
>
>
>
>
>


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

  reply	other threads:[~2003-08-14 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14 20:05 Hardware Requrements for Linux on 405GPr Stephen Williams
2003-08-14 20:17 ` Mark Hatle [this message]
2003-08-14 20:30   ` Stephen Williams
2003-08-15 21:05   ` Michael J. Accetta
2003-08-14 20:26 ` Wolfgang Denk

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=3F3BEE49.4050806@mvista.com \
    --to=fray@mvista.com \
    --cc=612dlag102@sneakemail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.