From: Rusty Lynch <rusty@linux.co.intel.com>
To: root@chaos.analogic.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
p_gortmaker@yahoo.com, lkml <linux-kernel@vger.kernel.org>,
rddunlap@osdl.org
Subject: Re: [2.5.63 PATCH][TRIVIAL]Change rtc.c ioport extend from 10h to 8h
Date: 26 Feb 2003 11:42:30 -0800 [thread overview]
Message-ID: <1046288552.4450.13.camel@vmhack> (raw)
In-Reply-To: <Pine.LNX.3.95.1030226142828.5091A-100000@chaos>
On Wed, 2003-02-26 at 11:35, Richard B. Johnson wrote:
> On 26 Feb 2003, Rusty Lynch wrote:
>
> > The real time clock only needs 8 bytes, but rtc.c is reserving 10h bytes.
> [SNIPPED...]
>
> It only needs two bytes port 0x70 and port 0x71 in ix86. Since the Sparc
> gets addressed differently and can only read/write words, it needs 8
> bytes. Please, if you are going to fix it, please fix it only once by
> setting a different length for the different machines!
> Cheers,
> Dick Johnson
Actually, it's finer grain then x86, it's a chipset issue. As Randy
pointed out in the original thread ==>
> Some Intel chipset specs list RTC as using 0x70 - 0x77, probably with
> some aliasing in there, so it looks to me like an EXTENT of 8 would be
> safer and still allow you access to 0x79.
>
> I'm looking at 82801BA-ICH2, 82801-ICH3, and 82801AA-ICH0 specs.
>
> --
> ~Randy
>
Any suggestions on the right way of doing this?
--rustyl
next prev parent reply other threads:[~2003-02-26 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 19:09 [2.5.63 PATCH][TRIVIAL]Change rtc.c ioport extend from 10h to 8h Rusty Lynch
2003-02-26 19:35 ` Richard B. Johnson
2003-02-26 19:42 ` Rusty Lynch [this message]
2003-02-26 20:29 ` Richard B. Johnson
2003-02-26 20:46 ` Randy.Dunlap
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=1046288552.4450.13.camel@vmhack \
--to=rusty@linux.co.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
--cc=rddunlap@osdl.org \
--cc=root@chaos.analogic.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