From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "Mikael Pettersson" <mikpe@csd.uu.se>, "Andi Kleen" <ak@suse.de>
Cc: "Vojtech Pavlik" <vojtech@suse.cz>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH][2.6][2/5]Support for HPET based timer
Date: Wed, 20 Aug 2003 10:01:53 -0700 [thread overview]
Message-ID: <C8C38546F90ABF408A5961FC01FDBF1902C7D1D6@fmsmsx405.fm.intel.com> (raw)
Yes. I hadn't thought about early_ioremap option. There seems to be
multiple ways of doing early ioremap: bt_ioremap() and boot_ioremap(). I
will look at them closer and work on changing HPET code to use one of
these in place of fixmap.
Thanks,
-Venkatesh
> -----Original Message-----
> From: Mikael Pettersson [mailto:mikpe@csd.uu.se]
> Sent: Wednesday, August 20, 2003 3:47 AM
> To: Andi Kleen
> Cc: Vojtech Pavlik; linux-kernel@vger.kernel.org; Pallipadi, Venkatesh
> Subject: Re: [PATCH][2.6][2/5]Support for HPET based timer
>
>
> Andi Kleen writes:
> > Vojtech Pavlik <vojtech@suse.cz> writes:
> >
> > > On Tue, Aug 19, 2003 at 05:18:50PM -0700, Pallipadi,
> Venkatesh wrote:
> > >
> > > > Fixmap is for HPET memory map address access. As the timer
> > > > initialization happen
> > > > early in the boot sequence (before vm initialization),
> we need to have
> > > > fixmap()
> > > > and fix_to_virt() to access HPET memory map address.
> > >
> > > Ahh, yes, you're right. You can't use ioremap at that
> time. Actually I
> > > did the same on x86_64 not only because of vsyscalls.
> >
> > iirc i386 has an ioremap_early or somesuch.
>
> bt_ioremap(). I wrote it to support early DMI scan so DMI data
> could be used to blacklist BIOSen that break local APICs.
> This was done pretty much just to handle Dell laptops.
>
next reply other threads:[~2003-08-20 17:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 17:01 Pallipadi, Venkatesh [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-26 23:50 Pallipadi, Venkatesh
2003-08-26 21:43 Mikael Pettersson
2003-08-26 18:31 Pallipadi, Venkatesh
2003-08-26 18:51 ` Andrew Morton
2003-08-26 18:55 ` Andrew Morton
2003-08-26 23:20 ` john stultz
[not found] <C8C38546F90ABF408A5961FC01FDBF1902C7D1C9@fmsmsx405.fm.intel.com.suse.lists.linux.kernel>
[not found] ` <20030820080513.GB17793@ucw.cz.suse.lists.linux.kernel>
2003-08-20 10:01 ` Andi Kleen
2003-08-20 10:47 ` Mikael Pettersson
2003-08-20 17:09 ` Dave Hansen
2003-08-20 1:30 Pallipadi, Venkatesh
2003-08-20 0:18 Pallipadi, Venkatesh
2003-08-20 8:05 ` Vojtech Pavlik
[not found] <mmZK.Q4.11@gated-at.bofh.it>
2003-08-19 22:41 ` Andi Kleen
2003-08-19 19:20 Pallipadi, Venkatesh
2003-08-19 22:39 ` Vojtech Pavlik
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=C8C38546F90ABF408A5961FC01FDBF1902C7D1D6@fmsmsx405.fm.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®