linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Newbury <steve@snewbury.org.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Naren Sankar <nsankar@broadcom.com>,
	Jarod Wilson <jarod@wilsonet.com>,
	Scott Davilla <davilla@4pi.com>,
	Manu Abraham <abraham.manu@gmail.com>
Subject: Re: [PATCH] staging: Merge Crystal HD driver with linuxtv.org
Date: Sun, 27 Oct 2013 18:15:18 +0000	[thread overview]
Message-ID: <1382897718.2598.37.camel@artifact> (raw)
In-Reply-To: <20131027162613.GA23822@kroah.com>

On Sun, 2013-10-27 at 09:26 -0700, Greg KH wrote:
> On Sun, Oct 27, 2013 at 05:12:18PM +0000, Steven Newbury wrote:
> > > And these patches do a lot of new work to the driver, I'd rather see it
> > > get fixed up properly and moved out of staging first, before adding new
> > > support to it, otherwise why is it in staging at all?
> > 
> > That last part it a good question, it's been sitting there for 3 years,
> > I assume there are specific things that need improving to get it out of
> > staging?  Would the changes in this patch, without the support for new
> > hw support be sufficient to get that to happen?  I can't test it without
> > that support though...
> 
> See the TODO file for a list of things that need to be resolved.


> - Testing
I can do this for BCM70015 only, hopefully somebody else can test with other
hardware.

> - Cleanup return codes
Specifics?

> - Cleanup typedefs
For the existing staging driver, this one appears done to me.  For the new
code, I notice I've allowed a few to slip back in, I'll fix this.

> - Allocate an Accelerator device class specific Major number,
>   since we don't have any other open sourced accelerators, it is the only
>   one in that category for now.
>   A somewhat similar device is the DXR2/3
Is there a reason this hasn't happened?  (staging drivers don't get new major
numbers allocated?) Did nobody actually request a new class, or has there 
been no agreement on how to proceed?


> 
> I've been remiss in deleting some of the staging drivers lately, and
> this one was on my shortlist for removal, but if you have hardware for
> it, and want to adopt it, I'll gladly take the patches for getting your
> stuff to work if you are going to work toward getting it out of staging.
> 
I'll get it fixed up, I've an incentive to keep it working to keep my
wife happy! ;-) (It enables the network media box in our bedroom to work
with HD content without the fan screaming!)



  reply	other threads:[~2013-10-27 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 16:27 [PATCH] staging: Merge Crystal HD driver with linuxtv.org Steven Newbury
2013-10-27 15:54 ` Greg KH
2013-10-27 17:12   ` Steven Newbury
2013-10-27 16:26     ` Greg KH
2013-10-27 18:15       ` Steven Newbury [this message]
2013-10-29 12:54         ` Steven Newbury
2013-10-29 14:51           ` Steven Newbury

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=1382897718.2598.37.camel@artifact \
    --to=steve@snewbury.org.uk \
    --cc=abraham.manu@gmail.com \
    --cc=davilla@4pi.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarod@wilsonet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsankar@broadcom.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).