public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Charles-Edouard Ruault <ce@idtect.com>
Cc: torvalds@osdl.org, akpm@osdl.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Reserve only needed regions for PC timers on i386 and x86_64
Date: Wed, 23 Feb 2005 04:23:58 -0300	[thread overview]
Message-ID: <20050223072358.GA6237@dmt.cnet> (raw)
In-Reply-To: <4219DCCA.1090509@idtect.com>


On Mon, Feb 21, 2005 at 02:06:18PM +0100, Charles-Edouard Ruault wrote:
> Alan Cox wrote:
> >On Llu, 2005-02-07 at 09:29, Charles-Edouard Ruault wrote:
> >>- Why is the generic timer using this address ? isn't it reserving a too 
> >>wide portion of IO ports ? Should it be modified for this board ?
> >
> >It just reserved the entire chip space since way back when.
> >>-  If there's a good reason for the timer to request this address, is  
> >>there a clean way to share it with the timer ?
> >
> >Submit a small patch to Linus/Andrew to make the generic code only
> >reserve the ports it should. It's just a historical oversight
> >
> > 
> >
> Linus, Andrew,
> As suggested by Alan, here's a small patch against kernel 2.4.29 to 
> split the IO addresses reserved for the  PC timer into two regions 
> instead of a large one.
> It mimics what has been done in kernel 2.6.
> Instead of reserving 0x40 through 0x5f it reserves only what the two 
> timers need, i.e 0x40-0x43 and 0x50-0x53.
> It patches both i386 and x86_64 architecture.

Applied, 

Thanks Charles.

> --- linux/arch/i386/kernel/setup.c.orig	Fri Feb 18 18:46:55 2005
> +++ linux/arch/i386/kernel/setup.c	Mon Feb 21 11:19:45 2005
> @@ -354,7 +354,8 @@
>  struct resource standard_io_resources[] = {
>  	{ "dma1", 0x00, 0x1f, IORESOURCE_BUSY },
>  	{ "pic1", 0x20, 0x3f, IORESOURCE_BUSY },
> -	{ "timer", 0x40, 0x5f, IORESOURCE_BUSY },
> +	{ "timer0", 0x40, 0x43, IORESOURCE_BUSY },
> +	{ "timer1", 0x50, 0x53, IORESOURCE_BUSY },
>  	{ "keyboard", 0x60, 0x6f, IORESOURCE_BUSY },
>  	{ "dma page reg", 0x80, 0x8f, IORESOURCE_BUSY },
>  	{ "pic2", 0xa0, 0xbf, IORESOURCE_BUSY },
> --- linux/arch/x86_64/kernel/setup.c.orig	Mon Feb 21 11:56:11 2005
> +++ linux/arch/x86_64/kernel/setup.c	Mon Feb 21 11:54:41 2005
> @@ -93,7 +93,8 @@
>  struct resource standard_io_resources[] = {
>  	{ "dma1", 0x00, 0x1f, IORESOURCE_BUSY },
>  	{ "pic1", 0x20, 0x3f, IORESOURCE_BUSY },
> -	{ "timer", 0x40, 0x5f, IORESOURCE_BUSY },
> +	{ "timer0", 0x40, 0x43, IORESOURCE_BUSY },
> +	{ "timer1", 0x50, 0x53, IORESOURCE_BUSY },
>  	{ "keyboard", 0x60, 0x6f, IORESOURCE_BUSY },
>  	{ "dma page reg", 0x80, 0x8f, IORESOURCE_BUSY },
>  	{ "pic2", 0xa0, 0xbf, IORESOURCE_BUSY },


      reply	other threads:[~2005-02-23 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07  9:29 IO port conflict between timer & watchdog on PCISA-C800EV board ? Charles-Edouard Ruault
2005-02-07 16:31 ` Randy.Dunlap
2005-02-07 17:00   ` linux-os
2005-02-07 17:33     ` Charles-Edouard Ruault
2005-02-07 17:32   ` Charles-Edouard Ruault
2005-02-07 17:57   ` Ondrej Zary
2005-02-15 17:04 ` Alan Cox
2005-02-21 13:06   ` [PATCH] Reserve only needed regions for PC timers on i386 and x86_64 Charles-Edouard Ruault
2005-02-23  7:23     ` Marcelo Tosatti [this message]

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=20050223072358.GA6237@dmt.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ce@idtect.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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