linux-kernel - Re: [PATCH v3] staging: add Broadcom Crystal HD driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7cdf10991001042310n2d750e0o3fddb047bf762871@mail.gmail.com>
Date:	Tue, 5 Jan 2010 02:10:56 -0500
From:	Jarod Wilson <jarodwilson@...il.com>
To:	"Naren (Narendra) Sankar" <nsankar@...adcom.com>
Cc:	"hancockrwd@...il.com" <hancockrwd@...il.com>,
	"jarod@...hat.com" <jarod@...hat.com>,
	"greg@...ah.com" <greg@...ah.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"davilla@....com" <davilla@....com>,
	"abraham.manu@...il.com" <abraham.manu@...il.com>
Subject: Re: [PATCH v3] staging: add Broadcom Crystal HD driver

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@...adcom.com> wrote:
> That is ok by us.
>
> The driver does only use a small subset.
>
> Naren
>
> ----- Original Message -----
> From: Jarod Wilson <jarodwilson@...il.com>
> To: Naren (Narendra) Sankar
> Cc: Robert Hancock <hancockrwd@...il.com>; Jarod Wilson <jarod@...hat.com>; Greg KH <greg@...ah.com>; linux-kernel@...r.kernel.org <linux-kernel@...r.kernel.org>; Scott Davilla <davilla@....com>; Manu Abraham <abraham.manu@...il.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@...adcom.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@...il.com]
>> Sent: Monday, January 04, 2010 6:22 PM
>> To: Jarod Wilson
>> Cc: Greg KH; linux-kernel@...r.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@...r.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@...il.com
>
>



-- 
Jarod Wilson
jarodwilson@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/