From: Timur Tabi <timur@tabi.org>
To: Scott Wood <scottwood@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
Aggrwal Poonam-B10812 <B10812@freescale.com>,
Jain Priyanka-B32167 <B32167@freescale.com>,
Kushwaha Prabhakar-B32579 <B32579@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Prabhakar Kushwaha <prabhakar@freescale.com>
Subject: Re: [PATCH 1/2][v3] powerpc/fsl-booke: Add initial T104x_QDS board support
Date: Fri, 20 Sep 2013 19:23:50 -0500 [thread overview]
Message-ID: <523CE716.70909@tabi.org> (raw)
In-Reply-To: <1379693218.16231.7.camel@aoeu.buserror.net>
Scott Wood wrote:
> The patch is not "lying". It is describing the board, not what the
> patch supports. This was something you used to constantly tell people
> to do...
The patch says:
"DIU supports video at up to 1280x1024x32bpp"
How is this not misleading?
I understand that the patch describes the board, and that's correct. It
should also indicate which major functionality is not supported. I was
expecting something like this:
- Video
- DIU hardware is capable of video up to 1280x1024x32bpp
- DIU support is currently not implemented
> There are other things in that description that Linux doesn't do
> anything with, such as QIXIS.
Fair enough, but the QIXIS is not something that would generally be
supported by Linux, as there is no "QIXIS driver". There is a DIU
driver, however.
The patch description should state which major components are not
currently supported by software, but would be expected to be supported.
next prev parent reply other threads:[~2013-09-21 0:23 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
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 [this message]
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=523CE716.70909@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 \
--cc=prabhakar@freescale.com \
--cc=scottwood@freescale.com \
/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).