public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: andrew@lunn•ch (Andrew Lunn)
To: linux-arm-kernel@lists•infradead.org
Subject: orion/kirkwood and device tree
Date: Mon, 7 Nov 2011 07:28:36 +0100	[thread overview]
Message-ID: <20111107062836.GG19491@lunn.ch> (raw)
In-Reply-To: <alpine.LFD.2.02.1111062046320.3307@xanadu.home>

> Beware. Moving the DRAM window setup code out of the various drivers is 
> not necessarily a good idea.  This setup is different from one 
> peripheral to another, and the associated registers are highly 
> peripheral specific.

Yes, i've noticed this. However, the core of the code is the same in
every case. So i think it should be possible. We will see.

      Andrew

  reply	other threads:[~2011-11-07  6:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111031105740.GC29402@lunn.ch>
     [not found] ` <20111031152100.GR32165@titan.lakedaemon.net>
     [not found]   ` <20111031164042.GD29402@lunn.ch>
2011-10-31 22:50     ` orion/kirkwood and device tree Michael Walle
2011-10-31 22:54       ` Russell King - ARM Linux
2011-11-01  6:25       ` Andrew Lunn
2011-11-02 16:50       ` Jason
2011-11-02 22:03         ` Michael Walle
2011-11-03 18:15           ` memory map in fdt was: " Jason
2011-11-03 18:47           ` Jason
2011-11-03 21:50             ` Michael Walle
2011-11-04  9:21               ` Simon Guinot
2011-11-16 23:34                 ` Michael Walle
2011-11-04 14:01               ` Nicolas Pitre
2011-11-06 23:12                 ` Michael Walle
2011-11-06 16:05       ` Andrew Lunn
2011-11-06 22:40         ` Michael Walle
2011-11-07  6:27           ` Andrew Lunn
2011-11-07  2:35         ` Nicolas Pitre
2011-11-07  6:28           ` Andrew Lunn [this message]
2011-11-06 16:07       ` [PATCH 1/1] [orion] Consolidate the address map setup on Orion based platforms Andrew Lunn

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=20111107062836.GG19491@lunn.ch \
    --to=andrew@lunn$(echo .)ch \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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