From: Jarod Wilson <jarodwilson@gmail.com>
To: "Naren (Narendra) Sankar" <nsankar@broadcom.com>
Cc: "hancockrwd@gmail.com" <hancockrwd@gmail.com>,
"jarod@redhat.com" <jarod@redhat.com>,
"greg@kroah.com" <greg@kroah.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davilla@4pi.com" <davilla@4pi.com>,
"abraham.manu@gmail.com" <abraham.manu@gmail.com>
Subject: Re: [PATCH v3] staging: add Broadcom Crystal HD driver
Date: Tue, 5 Jan 2010 02:10:56 -0500 [thread overview]
Message-ID: <7cdf10991001042310n2d750e0o3fddb047bf762871@mail.gmail.com> (raw)
In-Reply-To: <80A6ED01A151614884EE6C5D6AF0F2E90460683B6A@SJEXCHCCR01.corp.ad.broadcom.com>
Okay, cool. Greg, would you like an updated trimmed header before
adding this to staging, or can I just follow up later with a patch to
reduce the heft?
--jarod
On Tue, Jan 5, 2010 at 2:05 AM, Naren (Narendra) Sankar
<nsankar@broadcom.com> wrote:
> That is ok by us.
>
> The driver does only use a small subset.
>
> Naren
>
> ----- Original Message -----
> From: Jarod Wilson <jarodwilson@gmail.com>
> To: Naren (Narendra) Sankar
> Cc: Robert Hancock <hancockrwd@gmail.com>; Jarod Wilson <jarod@redhat.com>; Greg KH <greg@kroah.com>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>; Scott Davilla <davilla@4pi.com>; Manu Abraham <abraham.manu@gmail.com>
> Sent: Mon Jan 04 22:58:29 2010
> Subject: Re: [PATCH v3] staging: add Broadcom Crystal HD driver
>
> On Mon, Jan 4, 2010 at 9:36 PM, Naren (Narendra) Sankar
> <nsankar@broadcom.com> wrote:
>> The register bits come straight from the HW RTL. So this way there are no errors or typos. It would be easier for maintenance from our side since this is generated automagically. And when we add new HW, again it is a script that spews this out.
>>
>> Not absolutely necessary, but worried that cleanups may cause more problems than fix.
>
> I think the automation is worth it to a point, but this header does
> seem to be a wee bit excessive. I doubt if we're even using 1% of the
> ~12k defines in that one header, so we're bloating the code by a huge
> amount for relatively little benefit. Its probably worth maintaining
> the full register header *somewhere* (in with the userspace lib
> somewhere?), but maybe we just do a trimmed down version for the
> kernel module that contains only the bits we actually need.
>
>> -----Original Message-----
>> From: Robert Hancock [mailto:hancockrwd@gmail.com]
>> Sent: Monday, January 04, 2010 6:22 PM
>> To: Jarod Wilson
>> Cc: Greg KH; linux-kernel@vger.kernel.org; Scott Davilla; Naren (Narendra) Sankar; Manu Abraham
>> Subject: Re: [PATCH v3] staging: add Broadcom Crystal HD driver
>>
>> On 01/04/2010 05:34 PM, Jarod Wilson wrote:
>>> On 1/4/10 6:19 PM, Greg KH wrote:
>>>> On Mon, Jan 04, 2010 at 06:02:27PM -0500, Jarod Wilson wrote:
>>>>> This patch supersedes the earlier ones sent by Manu Abraham to add
>>>>> the Broadcom Crystal HD driver to the staging tree, per discussion
>>>>> with him about it. I've been working with Broadcom's Naren Sankar
>>>>> on this driver for a number of months, and had already talked Naren
>>>>> about submitting this on Broadcom's behalf, didn't expect anyone
>>>>> else to jump on submitting it as quickly as Manu did. ;)
>>>>
>>>> Looks good, I'll queue it up tomorrow.
>>>
>>> Nb: it looks like the thing is so massive (~935k), its not showing up on
>>> lkml (at least, not in a timely fashion), so for the interested:
>>>
>>> <http://people.redhat.com/jwilson/misc/broadcom-crystalhd-decoder-driver-staging.patch>
>>>
>>> Thanks much!
>>
>> Literally the majority of the code is #defines for what looks like
>> register bits, etc - is all that really necessary?
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
>
>
> --
> Jarod Wilson
> jarodwilson@gmail.com
>
>
--
Jarod Wilson
jarodwilson@gmail.com
next prev parent reply other threads:[~2010-01-05 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 7:05 Naren (Narendra) Sankar
2010-01-05 7:10 ` Jarod Wilson [this message]
2010-01-05 14:45 ` Greg KH
[not found] <20100104230227.GA14314@redhat.com>
2010-01-04 23:19 ` Greg KH
2010-01-04 23:34 ` Jarod Wilson
2010-01-05 2:21 ` Robert Hancock
2010-01-05 2:36 ` Naren (Narendra) Sankar
2010-01-05 6:58 ` Jarod Wilson
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=7cdf10991001042310n2d750e0o3fddb047bf762871@mail.gmail.com \
--to=jarodwilson@gmail.com \
--cc=abraham.manu@gmail.com \
--cc=davilla@4pi.com \
--cc=greg@kroah.com \
--cc=hancockrwd@gmail.com \
--cc=jarod@redhat.com \
--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
all inboxes | Powered by JetHome®