thomas schorpp wrote:

quoted text
>hi,
>
>Michael Renzmann wrote:
> =20
>
>>Hi.
>>
>>thomas schorpp wrote:
>>
>>   =20
>>
>>>ive tried to fix a major issue from the todo list here and ended up wi=
th
quoted text
>>>HW damage cause i had got no source of this buggy, not power-failsafe,
>>>proprietary hal provided by this project.
>>>     =20
>>>
>>To be frank, I'm simply pissed about your ranting here on this list.
>>   =20
>>
>
>thats your personal problem. my arguments are even better than Your lazy
>"lawyers" excuse to keep that hal closed due to fcc, and reasonable and
>technical, quality and economical funded. that had to be said. not
>mentioned the 50=80 damage i AND beat meier has suffered.
> =20
>

As I recall no one has forced anyone to use Atheros hardware. If there=20
are other vendor's products
that work better for you, by all means, use them.

If you are going to use Atheros hardware, then 1) present to Atheros a=20
business plan that is so inspiring
that they will see the great economic benefit by permiting you access to=20
their vxWorks/NDIS driver sources,
as well as detailed technical specs at the hardware level to allow you=20
any imaginable coding you require.
Or, 2) accept what Atheros is willing to give to the 'opensource', based=20
on their requirements of a 'closed' source
HAL that does not violate the the GPL, in the case of Linux, or any=20
other BSD style license in the case
of Free/Net-BSD.

Perhaps Broadcom+ndiswrapper is what is better suited to your needs.



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf