linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC,PATCH 3/3] arm: remove machine_desc.io_pg_offst and .phys_io
Date: Thu, 22 Jul 2010 10:46:43 +0100	[thread overview]
Message-ID: <20100722094643.GB31293@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1279703355.27276.100.camel@pororo.lan>

On Wed, Jul 21, 2010 at 11:09:15AM +0200, Jeremy Kerr wrote:
> Russell,
> 
> > It's extremely unlikely to have a UART at address 0 (because that's by
> > default where the CPU jumps to on reset.)  That's not to say it could
> > never happen - it's possible to hard-wire the CPU into 'hivec' mode
> > where it'll instead jump to 0xffff0000.  In that case, if you're sane
> > you'd put your SDRAM at 0x00000000.
> 
> OK, the patch I have just posted is a bit of a hack that does the 0x0
> check; happy to do this a different way.
> 
> So, the simplest solution seems to be to make the uart mapping code
> dependent on !DEBUG_ICEDCC (but leave the code there to add the mappings
> for ARCH_NETWINDER, ARCH_CATS and ARCH_RPC). Would you like a new patch
> for this?

I think the last patch you posted is fine as-is.  Compiling out the
setup code for the DEBUG_ICEDCC would be an optimization which could
be done though...  If you think it's appropriate, please do so.

Meanwhile, I'm happy enough to merge this patch (or the optimized one)
and the follow-on patch which kills off the initializers.

Out of interest, have the OMAP platforms been compile tested with this?

  reply	other threads:[~2010-07-22  9:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14  2:09 [RFC,PATCH 0/3] Allow late mdesc detection, v2 Jeremy Kerr
2010-07-14  2:09 ` [RFC,PATCH 2/3] arm: use addruart macro to establish debug mappings Jeremy Kerr
2010-07-14  3:58   ` [RFC, PATCH " Nicolas Pitre
2010-07-14  9:42     ` [RFC,PATCH " Jeremy Kerr
2010-07-14 12:38       ` [RFC, PATCH " Nicolas Pitre
2010-07-14  2:09 ` [RFC,PATCH 3/3] arm: remove machine_desc.io_pg_offst and .phys_io Jeremy Kerr
2010-07-20  9:14   ` [RFC, PATCH " Eric Miao
2010-07-20  9:22     ` Fwd: [RFC,PATCH " Eric Miao
2010-07-20 10:04     ` Russell King - ARM Linux
2010-07-20 10:21       ` Jeremy Kerr
2010-07-20 12:32         ` Jeremy Kerr
2010-07-21  8:50           ` Russell King - ARM Linux
2010-07-21  9:09             ` Jeremy Kerr
2010-07-22  9:46               ` Russell King - ARM Linux [this message]
2010-07-22 10:06                 ` Jeremy Kerr
2010-07-22 10:21                   ` Russell King - ARM Linux
2010-07-22 14:01                     ` Jeremy Kerr
2010-07-22 10:35                   ` Russell King - ARM Linux
2010-07-21 10:28             ` [RFC, PATCH " Nicolas Pitre
2010-07-22 11:42   ` [RFC,PATCH " Russell King - ARM Linux
2010-07-14  2:09 ` [RFC, PATCH 1/3] arm: return both physical and virtual addresses from addruart Jeremy Kerr
2010-07-15  2:48 ` [RFC,PATCH 0/3] Allow late mdesc detection, v2 Jeremy Kerr
2010-07-15  3:06   ` Eric Miao

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=20100722094643.GB31293@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).