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


Mark Hatle fray-at-mvista.com |PPC Linux Embedded| wrote:
> 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.

The first iteration of this device will HAVE a PCI connector and
go into a PCI slot of a host computer, but it will have a network
interface as well, to provide some minimal services such as a web
server for configuration and so forth. I can't thinkof anything
right off that will need the correct time, but who knows.

Well, actually there is logging.

As for memory, 64M of SDRAM w/ option for 128meg, and flash enough
to write a bootstrap loader to get the O/S off CompactFlash card.

--
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:30 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
2003-08-14 20:30   ` Stephen Williams [this message]
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=32336-60300@sneakemail.com \
    --to=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.