From: Karsten Jeppesen <kj-list@jeppesens.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.4 kernel on briQ - Available
Date: Sat, 18 May 2002 10:56:32 -0700 [thread overview]
Message-ID: <B90BE3DF.131F7%kj-list@jeppesens.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204092230310.25004-100000@blues.wcg.mcgill.ca>
Sorry for the long delay, but the Open Firmware had to be improved to allow
the BriQ its full potential as a CHRP computer.
Ben and I have been working very hard on this and successfully implemented
the BriQ into the 2.4 kernel tree.
I have uploaded all necessary software to
<http://www.tornado.totalimpact.com> also called the tornado site from which
it can be downloaded.
It includes 3 parts in 2 files.
- A preliminary manual (but they always are)
- The flash prom updater and the system software builder.
Sincerely,
Dr. Karsten Jeppesen
VP of Technology
Total Impact
<kj@totalimpact.com> Phn: (805) 987-8704 Fax: (805) 484-9469
-----------------------------------------------------------------------
Confidence is the feeling you have before you understand the situation.
-----------------------------------------------------------------------
>
> Just wondering if anyone has gotten a 2.4 kernel to compile and run on a
> briQ with 1GB of RAM?
>
> I have 4 of them that I have been playing with and would like to go into
> production very soon, and I'm just wondering if I should wait a little
> longer or stick with a 2.2 kernel and only 512 MB for now.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-18 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 2:32 2.4 kernel on briQ Christopher Murtagh
2002-04-10 9:08 ` benh
2002-04-10 13:47 ` Christopher Murtagh
2002-04-10 15:24 ` benh
2002-05-18 17:53 ` 2.4 kernel on briQ - Available Karsten Jeppesen
2002-05-18 21:50 ` Christopher Murtagh
2002-05-18 17:56 ` Karsten Jeppesen [this message]
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=B90BE3DF.131F7%kj-list@jeppesens.com \
--to=kj-list@jeppesens.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 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).