mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>,
	keith maanthey <kmannth@us.ibm.com>,
	Max Asbock <masbock@us.ibm.com>, Chris McDermott <lcm@us.ibm.com>,
	andrew@walrond.org
Subject: RE: i386 HPET code
Date: Thu, 03 Feb 2005 11:30:56 -0800	[thread overview]
Message-ID: <1107459056.2040.243.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6003EA715C@scsmsx403.amr.corp.intel.com>

On Thu, 2005-02-03 at 06:28 -0800, Pallipadi, Venkatesh wrote:
> Can you check whether only the following change makes the problem go
> away. If yes, then it looks like a hardware issue.
> 
> >	hpet_writel(hpet_tick, HPET_T0_CMP);
> >+	hpet_writel(hpet_tick, HPET_T0_CMP); /* AK: why twice? */
> >

Yep. Adding only the second write seems to make the box boot.

Since this isn't just affecting our hardware (see Andrew Walrond's
comment in the thread), would doing two writes like x86-64 does be
acceptable? 

thanks
-john



  reply	other threads:[~2005-02-03 19:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03 14:28 Pallipadi, Venkatesh
2005-02-03 19:30 ` john stultz [this message]
2005-02-03 20:02   ` Venkatesh Pallipadi
2005-02-03 21:22     ` Andi Kleen
2005-02-04 17:22     ` Andrew Walrond
2005-02-03 21:30 ` Andi Kleen
2005-02-04 19:28   ` Vojtech Pavlik
2005-02-04 20:02   ` Vojtech Pavlik
2005-02-04 20:03     ` Vojtech Pavlik
2005-02-04 23:41     ` [PATCH][i386] HPET setup, duplicate HPET_T0_CMP needed for some platforms Venkatesh Pallipadi
2005-02-05 10:55       ` Andrew Walrond
2005-02-06 15:58       ` Giuseppe Bilotta
  -- strict thread matches above, loose matches on Subject: below --
2005-02-03  2:05 i386 HPET code john stultz
2005-02-03  8:37 ` Andrew Walrond

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=1107459056.2040.243.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=ak@suse.de \
    --cc=andrew@walrond.org \
    --cc=kmannth@us.ibm.com \
    --cc=lcm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masbock@us.ibm.com \
    --cc=venkatesh.pallipadi@intel.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
all inboxes | Powered by JetHome®