From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: Ed Swierk <eswierk@aristanetworks.com>
Cc: rtc-linux@googlegroups.com, tglx@linutronix.de, mingo@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [rtc-linux] Re: [PATCH] x86: i2c rtc instead of cmos rtc
Date: Thu, 29 Jan 2009 22:19:25 +0100 [thread overview]
Message-ID: <20090129221925.07f5ab31@i1501.lan.towertech.it> (raw)
In-Reply-To: <9ae48b020901291312v459b4cddg4a991de2d4ef54bf@mail.gmail.com>
On Thu, 29 Jan 2009 13:12:49 -0800
Ed Swierk <eswierk@aristanetworks.com> wrote:
> > I object to options of this kind. It took us a lot of efforts to move
> > to the new i2c model and to the concept that devices have to be declared
> > in the board support code. This kind of hack is in the opposite direction.
>
> I see. I encountered board support code when I worked with PowerPC
> boards on Linux years ago but I haven't seen this in the x86 arch
> code. Can you point me to an example?
Under x86 the thing is not well defined, but you can check
arch/x86/kernel/olpc.c
for an example.
If you just have to load different modules I'd use an initrd
where you can place all the necessary logic to detect your board
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
prev parent reply other threads:[~2009-01-29 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 1:04 [PATCH] x86: i2c rtc instead of cmos rtc Ed Swierk
2009-01-27 11:21 ` Alessandro Zummo
2009-01-29 19:21 ` Ed Swierk
2009-01-29 19:41 ` [rtc-linux] " Alessandro Zummo
2009-01-29 20:05 ` Ed Swierk
2009-01-29 20:11 ` Alessandro Zummo
2009-01-29 21:12 ` Ed Swierk
2009-01-29 21:19 ` Alessandro Zummo [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=20090129221925.07f5ab31@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=eswierk@aristanetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rtc-linux@googlegroups.com \
--cc=tglx@linutronix.de \
/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