Re: request for information about the "ath5k" licensing

On Wed, Sep 05, 2007 at 01:00:15PM -0400, Luis R. Rodriguez wrote:

On 9/5/07, Michael Buesch [off-list ref] wrote:

quoted

On Wednesday 05 September 2007, Reyk Floeter wrote:

quoted

I'm the author of the free hardware driver layer for wireless Atheros
devices in OpenBSD, also known as "OpenHAL".

I'm still trying to get an idea about the facts and the latest state
of the incidence that violated the copyright of my code, because I
just returned from vacation.

quoted

Could you please give me some feedback about the latest state? Please
reply in private, I'm not subscribed to any of the Linux lists and I'm
rather interested in facts than in the usual trolling.

- Has this issue been fixed?

It has never been applied to any repository.
-> No issue and no copyright violation.

quoted

- Is there any repository available with the "ath5k" code using a
modified/"extended" license?

No.

Well that is not accurate. Please give us a few we are working on
verifying some information for you.

quoted

quoted

I don't know how to find the relevant bits in the various Linux git
repositories. Sorry, I don't get the structure of it. Are there any
other sources online except this diff on the linux kernel mailing
list?

- Are there any plans to release the "ath5k" code using a
modified/"extended" license?

No.

Same here. Apologies for this taking so long. It'll all be sorted out soon.

I'm still waiting for an answer. Your process is taking too long.

Reyk

Reyk Floeter wrote:

I'm still waiting for an answer. Your process is taking too long.

Speaking as a person through which these changes flow upstream into the 
official kernel (ath5k maintainers -> linville -> me -> linus)...


The most important thing for today is that no ath5k stuff has been 
committed (nor has it ever been).


I would rather take it slow and make sure everybody is happy.  There is 
nothing upstream, and so, there is no need to rush and correct something.

Collectively, this is just growing pains.  Everyone is breaking new 
ground, trying to figure out how to best support atheros stuff on Linux. 
  There are new tools to deal with (svn? git? flavor of the day?:)), new 
licenses with new ramifications to consider, a new wireless stack to 
deal with.

What you are witnessing is but a small part of the chaos as everyone 
tackles these chores simultaneously.

	Jeff