Menu
▾
▴
devil-linux-develop
|
From: Manu \MaNS\ E. <ee...@ma...> - 2004-01-03 06:35:46
|
Hi all,
Hope every one had good time for this new-years eve! ;-))
I'm working on the last hostap driver which is now 3 packages : the
driver, the utilities and the daemon. So I split the script in
build/scripts/ from hostap to hostap-driver, hostap-utils and hostapd;
then first build ... he couldn't find hostap script! In fact, i had to
manualy erase link in scripts/.buildorder and add the 3 new ones to make
it work ... also in rc1.d and rc2.d as i doesn't want an mrproper ;-)
The question is ... : do i have to add that link (in
scripts/.buildorder) myself or is the build system supposed to ? (sorry
for that, i didn't used the build system since 0.6 ...)
For the others, I guess the next time I run 'make mrproper unpack
menuconfig prepare build ...' the right links will be created in rc$.d
by the insserv thing!
I also modified things in scripts/configuration/ to reflect new
modifications
Am I missing something ?
Another question is : there's 2 ways to build the cardbus driver,
depending on which pcmcia support we will use : kernel or pcmcia_cs.
Does any one knows a {clean, clever...} way to copy them both in the
filesystem so we could choose the right one, depending on wether we use
pcmcia_cs or not (when DL is booted on a host), as they both have the
same name!
Maybe the question is non-sense as we use pcmcia_cs with no other choice?
Another thing is I'm on the way to add support for several other
wireless drivers (TI *ACX100, */Atmel AT76C5XXx, and Madwifi for
/Atheros AR500X chip sets) as i can have opportunity to hire some for
testing purpose. Is there any pb with madwifi as they are using a
binary-only HAL modul supported by Atheros ? the project seems GPLed
anyway ... http://sourceforge.net/projects/madwifi/
Cya
MaNU
|
|
From: Friedrich L. <fl...@fl...> - 2004-01-03 13:34:52
|
Manu "MaNS" ESCAR wrote on 03.01.2004 07:35 MET: > .....Is there any pb with madwifi as they are using a > binary-only HAL modul supported by Atheros ? the project seems GPLed > anyway ... http://sourceforge.net/projects/madwifi/ BUT please _do not_ include the binary drivers on the devil-cd. Rather make it download those files via wget from the internet as I would not want devil-lionux to get into a problems with those who own the rights of those binary-only modules. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Emmanuel E. <ee...@fr...> - 2004-01-03 14:38:21
|
Hi Friedrich!
here is the COPYRIGHT provided with tarball archive from sourceforge ...
All files contained in this distribution are covered by the following
copyright unless explicitly identified otherwise.
/*-
* Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer,
* without modification.
* 2. Redistributions in binary form must reproduce at minimum a disclai=
mer
* similar to the "NO WARRANTY" disclaimer below ("Disclaimer") and a=
ny
* redistribution must be conditioned upon including a substantially
* similar Disclaimer requirement for further binary redistribution.
* 3. Neither the names of the above-listed copyright holders nor the na=
mes
* of any contributors may be used to endorse or promote products der=
ived
* from this software without specific prior written permission.
*
* Alternatively, this software may be distributed under the terms of th=
e
* GNU General Public License ("GPL") version 2 as published by the Free
* Software Foundation.
*
* NO WARRANTY
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
* LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTIBILIT=
Y
* AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHAL=
L
* THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLAR=
Y,
* OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT =
OF
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSIN=
ESS
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
* IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHER=
WISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED O=
F
* THE POSSIBILITY OF SUCH DAMAGES.
*
* $Id: COPYRIGHT,v 1.3 2003/05/16 20:23:23 sam Exp $
*/
and here an extract of the README file ...
The ath_hal module contains the Atheros Hardware Access Layer (HAL).
This code manages much of the chip-specific operation of the driver.
The HAL is provided in a binary-only form in order to comply with FCC
regulations. In particular, a radio transmitter can only be operated at
power levels and on frequency channels for which it is approved. The FCC
requires that a software-defined radio cannot be configured by a user
to operate outside the approved power levels and frequency channels.
This makes it difficult to open-source code that enforces limits on
the power levels, frequency channels and other parameters of the radio
transmitter. See
http://ftp.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.pd=
f
for the specific FCC regulation. Because the module is provided in a
binary-only form it is marked "Proprietary"; this means when you load
it you will see messages that your system is now "tainted".
...
Is it a problem to comply with FCC regulations ? Is GPL v2 enough ?
there is a full gpl driver but, at this time, it's only capable of lightn=
ing the leds !
Furthermore, this driver is hostAP Capable ... so very interesting for us=
e with :
Netgear WAG511 & WAB501,
D-Link DWL-AG520, DWL-AG650 & DWL-AB650,
Linksys WPC55AG, WMP55AG & WPC51AB
for the most spreaded ...
Regards
MaNU
Friedrich Lobenstock a =E9crit:
> Manu "MaNS" ESCAR wrote on 03.01.2004 07:35 MET:
>=20
>> .....Is there any pb with madwifi as they are using a
>> binary-only HAL modul supported by Atheros ? the project seems GPLed=20
>> anyway ... http://sourceforge.net/projects/madwifi/
>=20
>=20
> BUT please _do not_ include the binary drivers on the devil-cd.
> Rather make it download those files via wget from the internet
> as I would not want devil-lionux to get into a problems with those
> who own the rights of those binary-only modules.
>=20
|
|
From: Friedrich L. <fl...@fl...> - 2004-01-03 15:11:24
|
Hi Emmanuel! Emmanuel ESCARABAJAL wrote on 03.01.2004 15:38 MET: > here is the COPYRIGHT provided with tarball archive from sourceforge ... > [..] > > and here an extract of the README file ... > > The ath_hal module contains the Atheros Hardware Access Layer (HAL). > This code manages much of the chip-specific operation of the driver. > The HAL is provided in a binary-only form in order to comply with FCC > regulations. In particular, a radio transmitter can only be operated at > power levels and on frequency channels for which it is approved. The FCC > requires that a software-defined radio cannot be configured by a user > to operate outside the approved power levels and frequency channels. > This makes it difficult to open-source code that enforces limits on > the power levels, frequency channels and other parameters of the radio > transmitter. See > > http://ftp.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.pdf > > for the specific FCC regulation. Because the module is provided in a > binary-only form it is marked "Proprietary"; this means when you load > it you will see messages that your system is now "tainted". But you have to check the page where the binary only stuff comes from if they allow packing or not and under which conditions. Remark: AFAIK please keep in mind that you need different HAL modules for Europe and the US as there are other frequencies involved in wireless lan here and there. > Is it a problem to comply with FCC regulations ? Is GPL v2 enough ? As said you have to check the licence of the binary-only stuff. The stuff under GPL is not a problem as it only loads and controls the most important binary-only part. > there is a full gpl driver but, at this time, it's only capable of > lightning the leds ! Sadly to hear that. > Furthermore, this driver is hostAP Capable ... so very interesting for > use with : > > Netgear WAG511 & WAB501, > D-Link DWL-AG520, DWL-AG650 & DWL-AB650, > Linksys WPC55AG, WMP55AG & WPC51AB > > for the most spreaded ... Yes I can follow you but if we get into commercial copyright law we have to be damned sure what we are including. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Emmanuel E. <ee...@fr...> - 2004-01-03 15:43:39
|
Hi,
i looked further in the distrib files and find one in the hal dir, specif=
icaly for the binary only=20
part :
All files contained in this distribution are covered by the following
copyright unless explicitly identified otherwise. Note that this
copyright does _NOT_ contain a "or GPL" clause and does _NOT_ permit
redistribution with changes.
/*-
* Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting, Atheros
* Communications, Inc. All rights reserved.
*
* Redistribution and use in source and binary forms are permitted
* provided that the following conditions are met:
* 1. The materials contained herein are unmodified and are used
* unmodified.
* 2. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following NO
* ''WARRANTY'' disclaimer below (''Disclaimer''), without
* modification.
* 3. Redistributions in binary form must reproduce at minimum a
* disclaimer similar to the Disclaimer below and any redistribution
* must be conditioned upon including a substantially similar
* Disclaimer requirement for further binary redistribution.
* 4. Neither the names of the above-listed copyright holders nor the
* names of any contributors may be used to endorse or promote
* product derived from this software without specific prior written
* permission.
*
* NO WARRANTY
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
* LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT,
* MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
* IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE
* FOR SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGES.
*
* $Id: COPYRIGHT,v 1.2 2003/06/25 04:50:21 sam Exp $
*/
"COPYRIGHT" 42L, 2116C=20
Is it Ok for You ? For me it is but i may have missunderstood important i=
mplications ...
Friedrich Lobenstock a =E9crit:
> Hi Emmanuel!
>=20
> Emmanuel ESCARABAJAL wrote on 03.01.2004 15:38 MET:
>=20
>> here is the COPYRIGHT provided with tarball archive from sourceforge .=
..
>> [..]
>>
>> and here an extract of the README file ...
>>
>> The ath_hal module contains the Atheros Hardware Access Layer (HAL).
>> This code manages much of the chip-specific operation of the driver.
>> The HAL is provided in a binary-only form in order to comply with FCC
>> regulations. In particular, a radio transmitter can only be operated =
at
>> power levels and on frequency channels for which it is approved. The =
FCC
>> requires that a software-defined radio cannot be configured by a user
>> to operate outside the approved power levels and frequency channels.
>> This makes it difficult to open-source code that enforces limits on
>> the power levels, frequency channels and other parameters of the radio
>> transmitter. See
>>
>> http://ftp.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264=
.pdf=20
>>
>>
>> for the specific FCC regulation. Because the module is provided in a
>> binary-only form it is marked "Proprietary"; this means when you load
>> it you will see messages that your system is now "tainted".
>=20
>=20
> But you have to check the page where the binary only stuff comes
> from if they allow packing or not and under which conditions.
>=20
> Remark: AFAIK please keep in mind that you need different
> HAL modules for Europe and the US as there are other
> frequencies involved in wireless lan here and there.
>=20
>> Is it a problem to comply with FCC regulations ? Is GPL v2 enough ?
>=20
>=20
> As said you have to check the licence of the binary-only stuff.
> The stuff under GPL is not a problem as it only loads and controls
> the most important binary-only part.
>=20
>> there is a full gpl driver but, at this time, it's only capable of=20
>> lightning the leds !
>=20
>=20
> Sadly to hear that.
So Do I! :-{
>=20
>> Furthermore, this driver is hostAP Capable ... so very interesting for=
=20
>> use with :
>>
>> Netgear WAG511 & WAB501,
>> D-Link DWL-AG520, DWL-AG650 & DWL-AB650,
>> Linksys WPC55AG, WMP55AG & WPC51AB
>>
>> for the most spreaded ...
>=20
>=20
> Yes I can follow you but if we get into commercial copyright law we
> have to be damned sure what we are including.
>=20
For sure, that's why I agree/apreciate your strictness !
Regards
|
|
From: Friedrich L. <fl...@fl...> - 2004-01-03 16:09:04
|
Emmanuel ESCARABAJAL wrote on 03.01.2004 16:43 MET:
> i looked further in the distrib files and find one in the hal dir,
> specificaly for the binary only part :
>
> All files contained in this distribution are covered by the following
> copyright unless explicitly identified otherwise. Note that this
> copyright does _NOT_ contain a "or GPL" clause and does _NOT_ permit
> redistribution with changes.
>
> /*-
> * Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting, Atheros
> * Communications, Inc. All rights reserved.
> *
> * Redistribution and use in source and binary forms are permitted
> * provided that the following conditions are met:
> * 1. The materials contained herein are unmodified and are used
> * unmodified.
> * 2. Redistributions of source code must retain the above copyright
> * notice, this list of conditions and the following NO
> * ''WARRANTY'' disclaimer below (''Disclaimer''), without
> * modification.
> * 3. Redistributions in binary form must reproduce at minimum a
> * disclaimer similar to the Disclaimer below and any redistribution
> * must be conditioned upon including a substantially similar
> * Disclaimer requirement for further binary redistribution.
> * 4. Neither the names of the above-listed copyright holders nor the
> * names of any contributors may be used to endorse or promote
> * product derived from this software without specific prior written
> * permission.
> *
> * NO WARRANTY
> * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> * ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> * LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT,
> * MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
> * IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE
> * FOR SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
> * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
> * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
> * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
> * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
> * SUCH DAMAGES.
> *
> * $Id: COPYRIGHT,v 1.2 2003/06/25 04:50:21 sam Exp $
> */
> "COPYRIGHT" 42L, 2116C
>
> Is it Ok for You ? For me it is but i may have missunderstood important
> implications ...
Ok that looks fine in regards to packaging with DL too me, but
according to §3 you have to print the "NO WARRANTY..." stuff.
Heiko what about adding such a "NO WARRANTY" for the whole DL
when it starts up? Could be useful for ourselfs ;-)
--
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock Linux Services Lobenstock
URL: http://www.lsl.at/ Email: fl...@fl...
____________________________________________________________________
|
|
From: Heiko Z. <he...@zu...> - 2004-01-03 16:23:20
|
Friedrich Lobenstock wrote:
> Emmanuel ESCARABAJAL wrote on 03.01.2004 16:43 MET:
>
>> i looked further in the distrib files and find one in the hal dir,
>> specificaly for the binary only part :
>>
>> All files contained in this distribution are covered by the following
>> copyright unless explicitly identified otherwise. Note that this
>> copyright does _NOT_ contain a "or GPL" clause and does _NOT_ permit
>> redistribution with changes.
>>
>> /*-
>> * Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting, Atheros
>> * Communications, Inc. All rights reserved.
>> *
>> * Redistribution and use in source and binary forms are permitted
>> * provided that the following conditions are met:
>> * 1. The materials contained herein are unmodified and are used
>> * unmodified.
>> * 2. Redistributions of source code must retain the above copyright
>> * notice, this list of conditions and the following NO
>> * ''WARRANTY'' disclaimer below (''Disclaimer''), without
>> * modification.
>> * 3. Redistributions in binary form must reproduce at minimum a
>> * disclaimer similar to the Disclaimer below and any redistribution
>> * must be conditioned upon including a substantially similar
>> * Disclaimer requirement for further binary redistribution.
>> * 4. Neither the names of the above-listed copyright holders nor the
>> * names of any contributors may be used to endorse or promote
>> * product derived from this software without specific prior written
>> * permission.
>> *
>> * NO WARRANTY
>> * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>> * ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>> * LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT,
>> * MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
>> * IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE
>> * FOR SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
>> * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
>> * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
>> * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
>> * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
>> * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
>> * SUCH DAMAGES.
>> *
>> * $Id: COPYRIGHT,v 1.2 2003/06/25 04:50:21 sam Exp $
>> */
>> "COPYRIGHT" 42L, 2116C
>>
>> Is it Ok for You ? For me it is but i may have missunderstood
>> important implications ...
>
>
> Ok that looks fine in regards to packaging with DL too me, but
> according to §3 you have to print the "NO WARRANTY..." stuff.
>
> Heiko what about adding such a "NO WARRANTY" for the whole DL
> when it starts up? Could be useful for ourselfs ;-)
>
Not a bad idea, where do you think we should add it, to the files issue.* ?
Heiko
|
|
From: Friedrich L. <fl...@fl...> - 2004-01-03 16:37:12
|
Heiko Zuerker wrote on 03.01.2004 17:22 MET: > Friedrich Lobenstock wrote: > >> Heiko what about adding such a "NO WARRANTY" for the whole DL >> when it starts up? Could be useful for ourselfs ;-) >> > > Not a bad idea, where do you think we should add it, to the files issue.* ? No not the issue files as I would only print it once after the boot process is finished. Either add a special start script or change /etc/init.d/rc for that to print it after a runlevel change from S to any number but not any more than that. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Emmanuel E. <ee...@fr...> - 2004-01-03 14:38:58
|
Any idea for the first part of the e-mail ??? Friedrich Lobenstock a =E9crit: > Manu "MaNS" ESCAR wrote on 03.01.2004 07:35 MET: >=20 >> .....Is there any pb with madwifi as they are using a >> binary-only HAL modul supported by Atheros ? the project seems GPLed=20 >> anyway ... http://sourceforge.net/projects/madwifi/ >=20 >=20 > BUT please _do not_ include the binary drivers on the devil-cd. > Rather make it download those files via wget from the internet > as I would not want devil-lionux to get into a problems with those > who own the rights of those binary-only modules. >=20 |
|
From: Friedrich L. <fl...@fl...> - 2004-01-03 15:13:24
|
Emmanuel ESCARABAJAL wrote on 03.01.2004 15:38 MET: > Any idea for the first part of the e-mail ??? > No. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Heiko Z. <he...@zu...> - 2004-01-03 15:43:21
|
Manu "MaNS" ESCAR wrote:
> Hope every one had good time for this new-years eve! ;-))
At least I had, how was yours?
> I'm working on the last hostap driver which is now 3 packages : the
> driver, the utilities and the daemon. So I split the script in
> build/scripts/ from hostap to hostap-driver, hostap-utils and hostapd;
> then first build ... he couldn't find hostap script! In fact, i had to
> manualy erase link in scripts/.buildorder and add the 3 new ones to make
> it work ... also in rc1.d and rc2.d as i doesn't want an mrproper ;-)
>
> The question is ... : do i have to add that link (in
> scripts/.buildorder) myself or is the build system supposed to ? (sorry
> for that, i didn't used the build system since 0.6 ...)
Whenever you add / remove / rename any build scripts, you have to re-run
"make prepare". You can run this any time, it will only re-order the
build scripts.
> For the others, I guess the next time I run 'make mrproper unpack
> menuconfig prepare build ...' the right links will be created in rc$.d
> by the insserv thing!
Yes.
> I also modified things in scripts/configuration/ to reflect new
> modifications
>
> Am I missing something ?
Did you also update the hostap.help file under configuration/help ?
> Another question is : there's 2 ways to build the cardbus driver,
> depending on which pcmcia support we will use : kernel or pcmcia_cs.
> Does any one knows a {clean, clever...} way to copy them both in the
> filesystem so we could choose the right one, depending on wether we use
> pcmcia_cs or not (when DL is booted on a host), as they both have the
> same name!
>
> Maybe the question is non-sense as we use pcmcia_cs with no other choice?
At the moment we only support the pcmcia_cs drivers, since the kernel
drivers are usually not as good. (Did that change lately ? )
> Another thing is I'm on the way to add support for several other
> wireless drivers (TI *ACX100, */Atmel AT76C5XXx, and Madwifi for
> /Atheros AR500X chip sets) as i can have opportunity to hire some for
> testing purpose. Is there any pb with madwifi as they are using a
> binary-only HAL modul supported by Atheros ? the project seems GPLed
> anyway ... http://sourceforge.net/projects/madwifi/
As Friedrich wrote, we need to be carefull about the copyrights.
Heiko
|
|
From: Emmanuel E. <ee...@fr...> - 2004-01-03 16:04:02
|
Heiko Zuerker a =E9crit:
> Manu "MaNS" ESCAR wrote:
>=20
>> Hope every one had good time for this new-years eve! ;-))
>=20
>=20
> At least I had, how was yours?
Great ;-))
>=20
>> I'm working on the last hostap driver which is now 3 packages : the=20
>> driver, the utilities and the daemon. So I split the script in=20
>> build/scripts/ from hostap to hostap-driver, hostap-utils and=20
>> hostapd; then first build ... he couldn't find hostap script! In fact,=
=20
>> i had to manualy erase link in scripts/.buildorder and add the 3 new=20
>> ones to make it work ... also in rc1.d and rc2.d as i doesn't want an=20
>> mrproper ;-)
>>
>> The question is ... : do i have to add that link (in=20
>> scripts/.buildorder) myself or is the build system supposed to ?=20
>> (sorry for that, i didn't used the build system since 0.6 ...)
>=20
>=20
> Whenever you add / remove / rename any build scripts, you have to re-ru=
n=20
> "make prepare". You can run this any time, it will only re-order the=20
> build scripts.
Nice ...
>> For the others, I guess the next time I run 'make mrproper unpack=20
>> menuconfig prepare build ...' the right links will be created in rc$.d=
=20
>> by the insserv thing!
>=20
>=20
> Yes.
>=20
>> I also modified things in scripts/configuration/ to reflect new=20
>> modifications
>>
>> Am I missing something ?
>=20
>=20
> Did you also update the hostap.help file under configuration/help ?
Not yet, but thanks, think I should have missed it ;-)
>=20
>> Another question is : there's 2 ways to build the cardbus driver,=20
>> depending on which pcmcia support we will use : kernel or pcmcia_cs.=20
>> Does any one knows a {clean, clever...} way to copy them both in the=20
>> filesystem so we could choose the right one, depending on wether we=20
>> use pcmcia_cs or not (when DL is booted on a host), as they both have=20
>> the same name!
>>
>> Maybe the question is non-sense as we use pcmcia_cs with no other choi=
ce?
>=20
>=20
> At the moment we only support the pcmcia_cs drivers, since the kernel=20
> drivers are usually not as good. (Did that change lately ? )
Maybe as SuSE 9.0 seems to work quite fine with, but i know they often ma=
ke lots of kernel patches=20
... anyway it greatly simplifies things for me;-))
>=20
>> Another thing is I'm on the way to add support for several other=20
>> wireless drivers (TI *ACX100, */Atmel AT76C5XXx, and Madwifi for=20
>> /Atheros AR500X chip sets) as i can have opportunity to hire some for=20
>> testing purpose. Is there any pb with madwifi as they are using a=20
>> binary-only HAL modul supported by Atheros ? the project seems GPLed=20
>> anyway ... http://sourceforge.net/projects/madwifi/
>=20
>=20
> As Friedrich wrote, we need to be carefull about the copyrights.
>=20
I try to be carefull with that, that's why i submit it to You All ... as =
my English et legal stuff=20
(mis)understanding may lead me in bad ways ... ;-)
Cya
MaNU
> Heiko
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills. Sign up for IBM=
's
> Free Linux Tutorials. Learn everything from the bash shell to sys admi=
n.
> Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>=20
>=20
|
|
From: Heiko Z. <he...@zu...> - 2004-01-03 16:11:20
|
Emmanuel ESCARABAJAL wrote: >>> Another thing is I'm on the way to add support for several other >>> wireless drivers (TI *ACX100, */Atmel AT76C5XXx, and Madwifi for >>> /Atheros AR500X chip sets) as i can have opportunity to hire some for >>> testing purpose. Is there any pb with madwifi as they are using a >>> binary-only HAL modul supported by Atheros ? the project seems GPLed >>> anyway ... http://sourceforge.net/projects/madwifi/ >> >> >> >> As Friedrich wrote, we need to be carefull about the copyrights. >> > > I try to be carefull with that, that's why i submit it to You All ... as > my English et legal stuff (mis)understanding may lead me in bad ways ... > ;-) > Not only you.... ;-) Heiko |
