public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Patard <apatard@mandriva.com>
To: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org, LKML <linux-kernel@vger.kernel.org>,
	huhb@lemote.com, yanh@lemote.com, Zhang Le <r0bertz@gentoo.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Nicholas Mc Guire <der.herr@hofr.at>,
	zhangfx@lemote.com, liujl@lemote.com
Subject: Re: [PATCH -queue v0 5/6] [loongson] rtc: enable legacy RTC driver on fuloong2f
Date: Wed, 04 Nov 2009 11:40:38 +0100	[thread overview]
Message-ID: <m3eioetvx5.fsf@anduin.mandriva.com> (raw)
In-Reply-To: <e13ed33a99dbf14f223360d414aa2b2c5caa9b1f.1257325319.git.wuzhangjin@gmail.com> (Wu Zhangjin's message of "Wed,  4 Nov 2009 17:06:07 +0800")

Wu Zhangjin <wuzhangjin@gmail.com> writes:

Hi,

> RTC_LIB is selected by MIPS by default, and therefore, the legacy RTC driver is
> disabled. but fortunately, RTC_LIB not works on fulong, so, enabling the legcy
> RTC driver is needed, otherwise, the tools like hwclock will not work.
>
> because loongson family machines, including fuloong2e, fuloong2f and
> yeeloong2f need to enable legacy RTC driver, so we use MACH_LOONGSON
> here.

There are loongson machines which are working fine with RTC_LIB (for
instance the gdium which is using a m41t83 on i2c) so would be better to
be more restrictive imho.

Arnaud

  reply	other threads:[~2009-11-04 10:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1257325319.git.wuzhangjin@gmail.com>
2009-11-04  9:04 ` [PATCH -queue v0 1/6] [loongson] add basic loongson-2f support Wu Zhangjin
2009-11-04 10:28   ` Arnaud Patard
2009-11-04 11:04     ` Wu Zhangjin
2009-11-04 11:19       ` Ralf Baechle
2009-11-04 15:23         ` Wu Zhangjin
2009-11-04 20:15           ` Ralf Baechle
2009-11-05  1:39             ` Wu Zhangjin
2009-11-05  8:45               ` Ralf Baechle
2009-11-04 11:36       ` Arnaud Patard
2009-11-05  9:18   ` Ralf Baechle
2009-11-05  9:48     ` Wu Zhangjin
2009-11-05 10:28       ` Ralf Baechle
2009-11-05 11:00         ` Wu Zhangjin
2009-11-04  9:05 ` [PATCH -queue v0 2/6] [loongson] oprofile: avoid do_IRQ for perfcounter when the interrupt is from bonito Wu Zhangjin
2009-11-04  9:05 ` [PATCH -queue v0 3/6] [loongson] add basic cs5536 vsm support Wu Zhangjin
2009-11-04  9:05 ` [PATCH -queue v0 4/6] [loongson] add basic fuloong2f support Wu Zhangjin
2009-11-05 13:16   ` Ralf Baechle
2009-11-05 14:44     ` Wu Zhangjin
2009-11-06  5:39     ` Wu Zhangjin
2009-11-06  8:30       ` Ralf Baechle
2009-11-06 10:05         ` Wu Zhangjin
2009-11-06  8:34     ` Wu Zhangjin
2009-11-04  9:06 ` [PATCH -queue v0 5/6] [loongson] rtc: enable legacy RTC driver on fuloong2f Wu Zhangjin
2009-11-04 10:40   ` Arnaud Patard [this message]
2009-11-04 11:18     ` Wu Zhangjin
2009-11-04 11:34       ` Arnaud Patard
2009-11-04 14:15       ` Ralf Baechle
2009-11-04 15:12         ` Wu Zhangjin
2009-11-04  9:06 ` [PATCH -queue v0 6/6] [loongson] add default config file for fuloong2f Wu Zhangjin

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=m3eioetvx5.fsf@anduin.mandriva.com \
    --to=apatard@mandriva.com \
    --cc=der.herr@hofr.at \
    --cc=huhb@lemote.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=liujl@lemote.com \
    --cc=r0bertz@gentoo.org \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.de \
    --cc=wuzhangjin@gmail.com \
    --cc=yanh@lemote.com \
    --cc=zhangfx@lemote.com \
    /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