* [PATCH][Trvial 2.5.59] rtc.c is requesting more ioports then it really uses
@ 2003-02-07 22:40 Rusty Lynch
2003-02-07 23:18 ` Randy.Dunlap
0 siblings, 1 reply; 3+ messages in thread
From: Rusty Lynch @ 2003-02-07 22:40 UTC (permalink / raw)
To: p_gortmaker; +Cc: lkml
I need to enable a device that talks to port 0x79h, but for some
reason the rtc is requesting move bytes then it really uses. Here
is a patch that makes the rtc only request what it uses.
--rustyl
--- drivers/char/rtc.c.orig 2003-02-07 14:35:31.000000000 -0800
+++ drivers/char/rtc.c 2003-02-07 13:25:45.000000000 -0800
@@ -47,7 +47,7 @@
#define RTC_VERSION "1.11"
-#define RTC_IO_EXTENT 0x10 /* Only really two ports, but... */
+#define RTC_IO_EXTENT 0x2
/*
* Note that *all* calls to CMOS_READ and CMOS_WRITE are done with
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH][Trvial 2.5.59] rtc.c is requesting more ioports then it really uses
2003-02-07 22:40 [PATCH][Trvial 2.5.59] rtc.c is requesting more ioports then it really uses Rusty Lynch
@ 2003-02-07 23:18 ` Randy.Dunlap
2003-02-09 8:47 ` Paul Gortmaker
0 siblings, 1 reply; 3+ messages in thread
From: Randy.Dunlap @ 2003-02-07 23:18 UTC (permalink / raw)
To: Rusty Lynch; +Cc: p_gortmaker, lkml
On 7 Feb 2003, Rusty Lynch wrote:
| I need to enable a device that talks to port 0x79h, but for some
| reason the rtc is requesting move bytes then it really uses. Here
| is a patch that makes the rtc only request what it uses.
|
| --rustyl
|
| --- drivers/char/rtc.c.orig 2003-02-07 14:35:31.000000000 -0800
| +++ drivers/char/rtc.c 2003-02-07 13:25:45.000000000 -0800
| @@ -47,7 +47,7 @@
|
| #define RTC_VERSION "1.11"
|
| -#define RTC_IO_EXTENT 0x10 /* Only really two ports, but... */
| +#define RTC_IO_EXTENT 0x2
|
| /*
| * Note that *all* calls to CMOS_READ and CMOS_WRITE are done with
| -
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH][Trvial 2.5.59] rtc.c is requesting more ioports then it really uses
2003-02-07 23:18 ` Randy.Dunlap
@ 2003-02-09 8:47 ` Paul Gortmaker
0 siblings, 0 replies; 3+ messages in thread
From: Paul Gortmaker @ 2003-02-09 8:47 UTC (permalink / raw)
To: Randy.Dunlap, Rusty Lynch; +Cc: p_gortmaker, lkml
Seems fine with me. If memory serves correctly the 0x10 came
from kernels prior to the rtc driver where the range was
requested as part of the generic i386 specific i/o space that
was off limits.
Paul.
--- "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> On 7 Feb 2003, Rusty Lynch wrote:
>
> | I need to enable a device that talks to port 0x79h, but for some
> | reason the rtc is requesting move bytes then it really uses. Here
> | is a patch that makes the rtc only request what it uses.
> |
> | --rustyl
> |
> | --- drivers/char/rtc.c.orig 2003-02-07 14:35:31.000000000 -0800
> | +++ drivers/char/rtc.c 2003-02-07 13:25:45.000000000 -0800
> | @@ -47,7 +47,7 @@
> |
> | #define RTC_VERSION "1.11"
> |
> | -#define RTC_IO_EXTENT 0x10 /* Only really two ports, but... */
> | +#define RTC_IO_EXTENT 0x2
> |
> | /*
> | * Note that *all* calls to CMOS_READ and CMOS_WRITE are done with
> | -
>
> 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
>
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-02-09 8:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-02-07 22:40 [PATCH][Trvial 2.5.59] rtc.c is requesting more ioports then it really uses Rusty Lynch
2003-02-07 23:18 ` Randy.Dunlap
2003-02-09 8:47 ` Paul Gortmaker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).