[lkml]   [2004]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Timer allocates too many ports
Randy.Dunlap wrote:

>On Fri, 20 Aug 2004 22:33:19 +0200 Pierre Ossman wrote:
>| Hi!
>| The timer in linux allocates the io ports 0x40 to 0x5F. This is causing
>| some problems for me since the hardware I'm writing a driver for has its
>| ports at 0x4E and 0x4F. In Windows the ports 0x40 to 0x43 are used for
>| the timer. Why does linux allocate so many more ports?
>Seems reasonable to me for Linux timer driver (resource) to allocate
>0x40 - 0x43 and 0x50 - 0x53 (on intel x86; only 0x40 - 0x43 for AMD x86-64).
>At least that's what is in some Intel specs. That would be accurate
>AFAIK and still leave 0x4e - 0x4f available.
Unfortunately the driver allocates 0x40-0x5f as can be seen in
0040-005f : timer
I do not know which file contains this allocation so I haven't been able
to change it. Any ideas?

>What kind of device uses IO addresses 0x4e - 0x4f?
>Is it a motherboard device? Intel ICH specs think that 0x4e - 0x4f
>are for LPC SIO and are forwarded to the LPC device.
The device is a SD/MMC card reader which is indeed an LPC device. The
ports in question are needed to identify the chip and determine which
resources it has. Actual usage is done on higher ports.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:05    [W:0.051 / U:1.488 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site