From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
To: Charles Manning <manningc2@actrix.gen.nz>
Cc: vb <vb@vsbe.com>, Paul Gortmaker <paul.gortmaker@gmail.com>,
Linux Embedded Maillist <linux-embedded@vger.kernel.org>,
corbet@lwn.net
Subject: Re: Adding a new platform
Date: Thu, 21 Aug 2008 10:46:48 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0808211044590.20704@vixen.sonytel.be> (raw)
In-Reply-To: <200808211502.58206.manningc2@actrix.gen.nz>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2095 bytes --]
On Thu, 21 Aug 2008, Charles Manning wrote:
> On Wednesday 20 August 2008 17:15:01 vb wrote:
> > On Tue, Aug 19, 2008 at 9:29 PM, Paul Gortmaker
> >
> > <paul.gortmaker@gmail.com> wrote:
> > > On Tue, Aug 19, 2008 at 11:57 PM, vb <vb@vsbe.com> wrote:
> > >> so, say a developer submits a proprietary driver and it gets accepted.
> > >
> > > Doesn't happen. By design. If the driver is proprietary then it is
> > > presumably not meant for open distribution, and hence not compatible with
> > > GPL and widespread distribution into 100,000 public git repositories. So
> > > it won't get submitted and it won't get accepted.
> >
> > I guess 'proprietary' is not the right term then, how do you call a
> > driver which is not a secret and not a problem to release, but
> > controls some hardware present in only in certain devices of a certain
> > company.
> >
> > Would such a driver be accepted? Wouldn't such a driver get stale
> > after a few kernel releases?
>
> In-tree is no silver bullet.
>
> When people modify internal APIs they will likely fix anything that breaks
> compilation. However many things are more subtle than that and it is very
> easy to end up with a driver or other code that compiles but does not work
> properly.
My experience with Linux/m68k tells me that +95% of the breakage is visible
by compiler warnings and errors. If it still compiles, it still works ;-)
> Luckily APIs for drivers (the most common stuff that people work on) don't
> change that much, and the interfaces are reasonably clear. If you want some
> hell then try working on file systems :-).
Really? So how come so few changes are needed to keep squashfs working?
With kind regards,
Geert Uytterhoeven
Software Architect
Sony Techsoft Centre Europe
The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium
Phone: +32 (0)2 700 8453
Fax: +32 (0)2 700 8622
E-mail: Geert.Uytterhoeven@sonycom.com
Internet: http://www.sony-europe.com/
A division of Sony Europe (Belgium) N.V.
VAT BE 0413.825.160 · RPR Brussels
Fortis · BIC GEBABEBB · IBAN BE41293037680010
next prev parent reply other threads:[~2008-08-21 8:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 18:01 Adding a new platform David VomLehn
2008-08-19 18:22 ` Ralf Baechle
2008-08-20 3:19 ` Paul Gortmaker
2008-08-20 3:57 ` vb
2008-08-20 4:29 ` Paul Gortmaker
2008-08-20 5:15 ` vb
2008-08-20 8:10 ` Haavard Skinnemoen
2008-08-20 15:39 ` vb
2008-08-21 3:02 ` Charles Manning
2008-08-21 8:40 ` David Woodhouse
2008-08-21 8:46 ` Geert Uytterhoeven [this message]
2008-08-21 8:48 ` David Woodhouse
2008-08-22 4:53 ` Phillip Lougher
2008-08-22 7:25 ` Peter Korsgaard
2008-08-20 4:44 ` Paul Mundt
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=Pine.LNX.4.64.0808211044590.20704@vixen.sonytel.be \
--to=geert.uytterhoeven@sonycom.com \
--cc=corbet@lwn.net \
--cc=linux-embedded@vger.kernel.org \
--cc=manningc2@actrix.gen.nz \
--cc=paul.gortmaker@gmail.com \
--cc=vb@vsbe.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).