From: Ingo Molnar <mingo@elte.hu>
To: Florian Fainelli <florian.fainelli@telecomint.eu>
Cc: Michael Buesch <mb@bu3sch.de>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH RFC] x86: Add user configurable GPIO-lib support
Date: Tue, 1 Jul 2008 16:26:43 +0200 [thread overview]
Message-ID: <20080701142643.GA20414@elte.hu> (raw)
In-Reply-To: <200807011455.56273.florian.fainelli@telecomint.eu>
* Florian Fainelli <florian.fainelli@telecomint.eu> wrote:
> > ... once that is made dynamic/quirkable we are there.
>
> Yes, I did not have time to investigate this, and am still wondering
> if we can have dynamic tick rate settings in early board setup code.
well, does the system have any early boot detectable property? Such as a
DMI signature? That way there would not be anything truly dynamic about
the PIT rate - we'd just set a new pit_tick_rate variable to a
non-default value very early during bootup, on an RDC system.
On usual PCs it would stay unmodified, at the default 1193182 value.
Ingo
next prev parent reply other threads:[~2008-07-01 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 10:49 [PATCH RFC] x86: Add user configurable GPIO-lib support Michael Buesch
2008-07-01 11:04 ` Ingo Molnar
2008-07-01 11:13 ` Michael Buesch
2008-07-01 11:19 ` Ingo Molnar
2008-07-01 11:27 ` Michael Buesch
2008-07-01 23:05 ` Michael Buesch
2008-07-01 12:55 ` Florian Fainelli
2008-07-01 14:26 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-02 2:57 David Brownell
2008-07-02 9:40 ` Michael Buesch
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=20080701142643.GA20414@elte.hu \
--to=mingo@elte.hu \
--cc=florian.fainelli@telecomint.eu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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