From: Timur Tabi <timur@tabi.org>
To: Kushwaha Prabhakar-B32579 <B32579@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
Jain Priyanka-B32167 <B32167@freescale.com>,
Aggrwal Poonam-B10812 <B10812@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/2][v3] powerpc/fsl-booke: Add initial T104x_QDS board support
Date: Thu, 19 Sep 2013 22:08:05 -0500 [thread overview]
Message-ID: <523BBC15.8030607@tabi.org> (raw)
In-Reply-To: <071A08F2C6A57E4E94D980ECA553F874F9CF8D@039-SN1MPN1-005.039d.mgd.msft.net>
Kushwaha Prabhakar-B32579 wrote:
> My primary object is to put base patch in Linux. once it done other things can be enabled one by one.
Any features which are not enabled must be specified in the patch
description. The patch says that the board supports DIU, but the code
doesn't, so that's misleading.
> Also, I am not familiar with DIU driver:(.
I can help you with the DIU driver.
> shall I remove the DIU node, and while adding support of DIU, all modification will be sent.
I think it should be okay to leave the DIU node. I think the kernel
will crash if you try to enable a DIU console (video= on the kernel
command line), but I think it's okay to ignore that for the moment.
next prev parent reply other threads:[~2013-09-20 3:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 9:00 [PATCH 1/2][v3] powerpc/fsl-booke: Add initial T104x_QDS board support Prabhakar Kushwaha
2013-09-19 20:32 ` Timur Tabi
2013-09-20 1:38 ` Kushwaha Prabhakar-B32579
2013-09-20 3:08 ` Timur Tabi [this message]
2013-09-20 8:46 ` Prabhakar Kushwaha
2013-09-20 11:55 ` Timur Tabi
2013-09-20 16:06 ` Scott Wood
2013-09-21 0:23 ` Timur Tabi
2013-09-23 18:06 ` Scott Wood
2013-09-24 23:25 ` Scott Wood
2013-09-25 0:18 ` Timur Tabi
2013-09-20 16:14 ` Scott Wood
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=523BBC15.8030607@tabi.org \
--to=timur@tabi.org \
--cc=B07421@freescale.com \
--cc=B10812@freescale.com \
--cc=B32167@freescale.com \
--cc=B32579@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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).