All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mpq101: initial support for Mercury Computer Systems MPQ101 board
Date: Mon, 17 Jan 2011 22:32:47 -0600	[thread overview]
Message-ID: <5139DB04-989B-46BA-82C8-25026476BB06@kernel.crashing.org> (raw)
In-Reply-To: <20110117223809.9D33ED1CAD5@gemini.denx.de>


On Jan 17, 2011, at 4:38 PM, Wolfgang Denk wrote:

> Dear Alex Dubov,
> 
> In message <369392.26813.qm@web37607.mail.mud.yahoo.com> you wrote:
>>> 
>>> Could you please be a bit more specific, i. e. like quoting
>>> file names
>>> and line numbers?
>>> 
>> 
>> These were produced by 
>> grep -nr ddr\-\> board/ | grep -v out_be
>> 
>> I can attach a listing, but it should be quicker this way.
>> Up until now it seemed a rather common practice to initialize ddr
>> controllers directly, bypassing io accessors.
> 
> Indeed. Even after the recent removal of some boards this list
> remains:
> 
> 	board/freescale/mpc8349itx/mpc8349itx.c
> 	board/freescale/mpc8536ds/mpc8536ds.c
> 	board/freescale/mpc8540ads/mpc8540ads.c
> 	board/freescale/mpc8560ads/mpc8560ads.c
> 	board/freescale/mpc8569mds/mpc8569mds.c
> 	board/freescale/mpc8572ds/mpc8572ds.c
> 	board/freescale/mpc8610hpcd/mpc8610hpcd.c
> 	board/freescale/mpc8641hpcn/mpc8641hpcn.c
> 	board/freescale/p2020ds/p2020ds.c
> 	board/sbc8560/sbc8560.c
> 	board/sbc8641d/sbc8641d.c
> 	board/socrates/sdram.c
> 	board/tqc/tqm85xx/sdram.c
> 
> Kumar, Andy - do you have any plans to fix this for the freescale
> boards?
> 
> Best regards,
> 
> Wolfgang Denk

I don't have an plans to fix this, however we can add it to the TODO list.  Just isn't high priority at this point.

- k

  reply	other threads:[~2011-01-18  4:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27  6:22 [U-Boot] [PATCH] mpq101: initial support for Mercury Computer Systems MPQ101 board Alex Dubov
2010-12-27 12:12 ` Wolfgang Denk
2010-12-28  4:42   ` Alex Dubov
2011-01-10 22:43     ` Wolfgang Denk
2011-01-11  3:14       ` Alex Dubov
2011-01-11  5:43         ` Wolfgang Denk
2011-01-11  7:32           ` Alex Dubov
2011-01-17 22:38             ` Wolfgang Denk
2011-01-18  4:32               ` Kumar Gala [this message]
2010-12-28  5:53   ` Alex Dubov
2011-01-10 22:49     ` Wolfgang Denk
2011-01-07  7:16   ` [U-Boot] [PATCH v3] " Alex Dubov
2011-01-10 22:56     ` Wolfgang Denk
2011-01-11  2:44       ` Alex Dubov
2011-01-11  7:43         ` Wolfgang Denk
2011-01-13  2:42           ` Alex Dubov
2011-01-14  9:10       ` [U-Boot] [PATCH v4] " Alex Dubov
2011-01-14 11:49         ` Kumar Gala
2011-01-17  3:07           ` Alex Dubov
2011-01-17  7:26           ` [U-Boot] [PATCH v5] " Alex Dubov
2011-01-18  5:15             ` Kumar Gala
2011-01-18  8:03               ` [U-Boot] [PATCH v6] " Alex Dubov
2011-01-18  9:42                 ` Kumar Gala
2011-01-19  9:50                   ` Alex Dubov
2011-01-20  5:02                   ` [U-Boot] [PATCH v7] " Alex Dubov
2011-01-20  7:50                     ` Kumar Gala
2011-01-24  5:59                       ` [U-Boot] [PATCH v8] " Alex Dubov
2011-01-27  5:45                         ` Kumar Gala
2011-01-27  8:41                           ` Alex Dubov
2011-01-20  8:46                     ` [U-Boot] [PATCH v7] " Wolfgang Denk
2011-01-22  7:27                       ` Alex Dubov
2011-01-14 11:51         ` [U-Boot] [PATCH v4] " Kumar Gala

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=5139DB04-989B-46BA-82C8-25026476BB06@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.