From: Matt Porter <mporter@kernel•crashing.org>
To: "Goforth, Edward" <Ed.Goforth@gd-ais•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: board with no RTC
Date: Thu, 13 Jan 2005 09:26:38 -0700 [thread overview]
Message-ID: <20050113092638.B25004@home.com> (raw)
In-Reply-To: <9A48EF7239039B48834A3F6B644B0C71EF8750@vaff06-mail01.ad.gd-ais.com>; from Ed.Goforth@gd-ais.com on Thu, Jan 13, 2005 at 10:14:20AM -0500
On Thu, Jan 13, 2005 at 10:14:20AM -0500, Goforth, Edward wrote:
> Thanks to everyone who responded. Now that a RTC is not a requirement,
> can anyone offer advice on what I will need to do to get the kernel
> (2.4.18) to play nice?
Are you using the linuxppc-2.4 tree? If you want up to date 2.4 4xx
support you should be using that tree as a starting point. Support
is better yet in 2.6 where most developers are spending their time.
-Matt
next prev parent reply other threads:[~2005-01-13 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 15:14 board with no RTC Goforth, Edward
2005-01-13 16:26 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-12 23:25 Goforth, Edward
2005-01-12 23:42 ` Eugene Surovegin
2005-01-12 23:48 ` Matt Porter
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=20050113092638.B25004@home.com \
--to=mporter@kernel$(echo .)crashing.org \
--cc=Ed.Goforth@gd-ais$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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