public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: vikasm <vikas.manocha@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/4] add support for new arch stv0991
Date: Tue, 25 Nov 2014 12:13:11 -0800	[thread overview]
Message-ID: <5474E2D7.8000202@st.com> (raw)
In-Reply-To: <5474DD69.4070801@st.com>

Hi Simon,

On 11/25/2014 11:50 AM, vikasm wrote:
> Hello Simon,
>
> On 11/18/2014 10:17 AM, vikasm wrote:
>> Hello Simon,
>>
>> On 11/17/2014 09:19 PM, Simon Glass wrote:
>>> Hi Vikas,
>>>
>>> On 18 November 2014 01:30, Vikas Manocha <vikas.manocha@st.com> wrote:
>>>> This patchset add support for new arch stv0991.
>>>>
>>>> Changes in v4:
>>>> - rebased to current master
>>>> - added maintainers info
>>>>
>>>> Changes in v3:
>>>> - removed period from commit messages
>>>>
>>>> Changes in v2:
>>>> - corrected files license to GPL-2.0+
>>>> - replaced printf() usage with puts() for string print
>>>> - sorted sourcing of board Kconfig
>>>>
>>>> Vikas Manocha (4):
>>>>    stv0991: Add basic stv0991 architecture support
>>>>    stv0991: enable ethernet support
>>>>    stv0991: default + misc command configs enabled
>>>>    stv0991: add maintainer information
>>> Can you please look at using driver model for this board? It would be
>>> particularly valuable since it looks like you are using the pl011 UART
>>> which has not previously been tested with driver model (and it seems
>>> you found some problems).
>>>
>>> To do this you probably only need to adjust a few defines and add
>>> platform data for serial. A patch for Raspberry Pi is here:
>>>
>>> http://patchwork.ozlabs.org/patch/392180/
>>
>> Sure, Simon. Infact i was also planning to use the driver model.
>> Thanks for sharing the Raspberry patch link.
>
> I tried using driver model but got into issue after relocation, 
> figured out that it was because 0x0 location
> was being overwritten & pl011 base address was being stored here...
> After tracking "Raspberry Pi with driver model" discussion, seems like 
> you are aware of it now, just wanted
> to provide this information on one more platform.

& with ".priv_auto_alloc_size = sizeof(struct pl01x_priv)," addition, 
the issue is fixed.

>
> Rgds,
> Vikas

Rgds,
Vikas

  reply	other threads:[~2014-11-25 20:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  1:30 [U-Boot] [PATCH v4 0/4] add support for new arch stv0991 Vikas Manocha
2014-11-18  1:30 ` [U-Boot] [PATCH v4 1/4] stv0991: Add basic stv0991 architecture support Vikas Manocha
2014-11-18  7:21   ` Albert ARIBAUD
2014-11-18 18:08     ` vikasm
2014-11-18  1:30 ` [U-Boot] [PATCH v4 2/4] stv0991: enable ethernet support Vikas Manocha
2014-11-18  1:30 ` [U-Boot] [PATCH v4 3/4] stv0991: default + misc command configs enabled Vikas Manocha
2014-11-18  7:29   ` Albert ARIBAUD
2014-11-18 18:10     ` vikasm
2014-11-18  1:30 ` [U-Boot] [PATCH v4 4/4] stv0991: add maintainer information Vikas Manocha
2014-11-18  5:19 ` [U-Boot] [PATCH v4 0/4] add support for new arch stv0991 Simon Glass
2014-11-18 18:17   ` vikasm
2014-11-25 19:50     ` vikasm
2014-11-25 20:13       ` vikasm [this message]
2014-11-25 20:26       ` Simon Glass

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=5474E2D7.8000202@st.com \
    --to=vikas.manocha@st.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox