public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx•de>
To: linuxppc-dev@ozlabs•org
Subject: Re: All your drivers are belong to us
Date: Thu, 08 May 2008 15:28:49 +0200	[thread overview]
Message-ID: <m2prrwsz5a.fsf_-_@ohwell.denx.de> (raw)
In-Reply-To: 20080507194957.47abb103@zod.rchland.ibm.com

Hi,

> On Wed, 7 May 2008 17:42:51 -0400
> Sean MacLennan <smaclennan@pikatech•com> wrote:
>
>> On Wed, 07 May 2008 16:36:30 +0200
>> "Detlev Zundel" <dzu@denx•de> wrote:
>> 
>> > It also happened that a driver once posted for what the customer
>> > thought was a completely specific device of his own today supports
>> > lots of different boards from at least four different manufacturers."
>> > 
>> > The wording is of course not exact but I hope I caught the spirit of
>> > what Greg wanted to say.  So yes, please post the driver - maybe Greg
>> > KH will tunnel it into mainline...
>> 
>> I agree with the sentiment. However, it is hard enough to get
>> legitimate drivers into the kernel. The drivers I mentioned do not
>> come close to following the Linux kernel coding spec.
>
> Here's the cool part.  There's this Linux driver project:
>
> http://www.linuxdriverproject.org/twiki/bin/view
>
> where they can take drivers like that and clean them up.  At least to a
> reasonable degree.  The benefit for you is that once it's cleaned up,
> it can go into the mainline kernel and it will just be there in future
> releases.  Helpful when you update.

Yes, I should have mentioned this also in my original mail.  If I
remember correctly, Greg mentioned that in this project, he has *300*
developers waiting to do something.  None of the companies previously
claiming Linux had a driver problem showed up even when he contacted
them directly....

> Now, I can't say I've personally ever used that project but its mission
> does seem pretty targeted towards groups that want to do the right
> thing with respect to drivers.  Maybe you could give it a shot and tell
> others about the experience.

This would definitely be interesting.

Cheers
  Detlev

-- 
-- Question authority!
-- Yeah, says who?
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx•de

      parent reply	other threads:[~2008-05-08 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  0:41 WARNING: mutexes are preferred for single holder semaphores Sean MacLennan
2008-05-05  1:06 ` Michael Ellerman
2008-05-05  1:31   ` Sean MacLennan
2008-05-05  2:13 ` Paul Mackerras
2008-05-05  6:01   ` Christoph Hellwig
2008-05-05  3:38 ` Benjamin Herrenschmidt
2008-05-05  4:40   ` Sean MacLennan
2008-05-07 14:36     ` All your drivers are belong to us [was WARNING: mutexes are preferred for single holder semaphores] Detlev Zundel
2008-05-07 21:42       ` All your drivers are belong to us [was WARNING: mutexes are preferredfor " Sean MacLennan
2008-05-08  0:49         ` Josh Boyer
2008-05-08  4:41           ` Sean MacLennan
2008-05-08 13:28           ` Detlev Zundel [this message]

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=m2prrwsz5a.fsf_-_@ohwell.denx.de \
    --to=dzu@denx$(echo .)de \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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