From: Andrew Victor <andrew@sanpeople.com>
To: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
Russell King <rmk@arm.linux.org.uk>,
alan@lxorguk.ukuu.org.uk, dwmw2@infradead.org
Subject: Re: [RFC] Atmel-supplied hardware headers for AT91RM9200 SoC processor
Date: 11 Jul 2005 15:57:26 +0200 [thread overview]
Message-ID: <1121090246.7380.46.camel@fuzzie.sanpeople.com> (raw)
In-Reply-To: <1121088922.7407.64.camel@localhost.localdomain>
hi,
> > No reason to use the horror it is as-is. Beein hardware description they
> > won't change ever except for additions, so just clean the mess up into
> > somethign nice and submit them. You could have done so in the time you
> > spent arguing on linux-arm-kernel already.
>
> Or written a perl script to reprocess them into something saner for
> that matter.
The issue that everybody seems to be forgetting (or ignoring) with
changing the headers is that ALL the drivers then also need to be
converted, and re-tested.
> The licensing does look problematic - perhaps Atmel will be happy to
> dual license them (see the many BSD bits of code that are in kernel
> and say things like "or at your option you may use the GNU Public
> License version 2 or later" and similar.
I have asked Atmel if they're willing to dual-license the headers. The
licensing issue is probably now with their legal department, but I don't
see them having a problem with it.
Regards,
Andrew Victor
next prev parent reply other threads:[~2005-07-11 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 9:58 Andrew Victor
2005-07-07 13:06 ` Christoph Hellwig
2005-07-11 13:35 ` Alan Cox
2005-07-11 13:57 ` Andrew Victor [this message]
2005-07-11 15:20 ` Alan Cox
2005-07-11 15:48 ` Christoph Hellwig
2005-07-07 14:41 ` David Woodhouse
2005-07-07 15:14 ` Andrew Victor
2005-07-07 15:26 ` David Woodhouse
2005-07-07 21:52 ` Alexey Dobriyan
2005-07-08 7:10 ` Andrew Victor
2005-07-08 14:50 ` Ben Dooks
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=1121090246.7380.46.camel@fuzzie.sanpeople.com \
--to=andrew@sanpeople.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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®