linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gary Thomas <gdt@linuxppc.org>
To: Pink X <PinkX@earthlink.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: RE: Embedded ppc project
Date: Fri, 22 Jan 1999 14:25:03 -0000 (GMT)	[thread overview]
Message-ID: <XFMail.990122142503.gdt@linuxppc.org> (raw)
In-Reply-To: <199901220857.AAA10924@avocet.prod.itd.earthlink.net>



On 22-Jan-99 Pink X wrote:
> 
> 
> Can someone give me  a brief overview of how the boot process works for 
> linuxppc on non-mac, non-open firmware hardware?
> 
> For instance, we're looking at a custom processor board for a project... 
> basically it will have a CPU, a DiskOnChip of about 24MB, RAM and a 
> drive.   Will it be hugely difficult to get linuxppc to boot out of the 
> DoC (with a kernal and compress root ramdisk in the DiskOnChip)  Does the 
> kernel make assumptions about there being certain types of hardware or a 
> open firmware roms being there?  Will it be hugely difficult for (very 
> experienced programmers who have worked on unix but not linux 
> specifically) to get the kernal hacked to our hardware formfactor (not 
> counting any I/O work, just booting in this environment.)
> 
> Any advice appreciated!  We may go with the RPCLite board, but we kinda 
> need a 603e level of power.  (So any 603e @200+MHz embedded boards would 
> be great to hear about, we've not found any yet.)
> 

One place to look is:
  Cogent Computer Systems
  (508) 278-9400
  http://www.cogcomp.com/


------------------------------------------------------------------------
Gary Thomas                              |
email: gdt@linuxppc.org                  | "Fine wine is a necessity of
   ... opinions expressed here are mine  |        life for me"
       and no one else would claim them! |
                                         |      Thomas Jefferson
------------------------------------------------------------------------



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1999-01-22 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-22  8:57 Embedded ppc project Pink X
1999-01-22 14:25 ` Gary Thomas [this message]
1999-01-22 15:38 ` Matt Porter
1999-01-22 16:41 ` Troy Benjegerdes

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=XFMail.990122142503.gdt@linuxppc.org \
    --to=gdt@linuxppc.org \
    --cc=PinkX@earthlink.net \
    --cc=linuxppc-dev@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).