From: Tom Rini <trini@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-embedded@lists.linuxppc.org, Matt Porter <porter@cox.net>
Subject: Re: Incoming to hostme.bitkeeper.com:/ua/repos/p/ppc/linuxppc-2.5
Date: Mon, 6 Jan 2003 08:45:23 -0700 [thread overview]
Message-ID: <20030106154523.GA796@opus.bloom.county> (raw)
In-Reply-To: <200301061203.EAA16917@hostme.bitkeeper.com>
On Mon, Jan 06, 2003 at 04:03:28AM -0800, ppc@bkbits.net wrote:
> ChangeSet@1.778, 2003-01-06 21:55:54+11:00, paulus@samba.org
> Small walnut update: don't reference todc_* unless CONFIG_GEN_RTC
> is set, plus minor syntax fix.
>
> arch/ppc/platforms/4xx/walnut.c@1.9, 03-01-06 21:55:49+11:00, paulus@samba.org
> take out parentheses in #ifdef, add #ifdef CONFIG_GEN_RTC around
> todc_* references
Ack! I really think this is the wrong approach, as now CONFIG_GEN_RTC=m
will still not work on Walnut (/ 40x in general). I think what we
really need is on 40x to either mimic how the 'classic' boards do it,
and have CONFIG_WALNUT, CONFIG_ASH, etc reference todc_time.o, and
always get it, or start defining attributes like had been suggested many
times in the past (ie a walnut, ash, spruce and so on would set
CONFIG_PPC32_USE_TODC_SUPPORT or something).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-01-06 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200301061203.EAA16917@hostme.bitkeeper.com>
2003-01-06 15:45 ` Tom Rini [this message]
[not found] <20020827120046.DCE42FC70@hostme.bitkeeper.com>
2002-08-27 12:27 ` Incoming to hostme.bitkeeper.com:/ua/repos/p/ppc/linuxppc-2.5 Geert Uytterhoeven
2002-08-27 12:59 ` Paul Mackerras
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=20030106154523.GA796@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=porter@cox.net \
/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.