Thread: Re: [Madwifi-users] binary only HAL causes me EXTREME grief! (Page 2)
Status: Beta
Brought to you by:
otaku
From: Thorsten v. E. <tv...@vo...> - 2005-10-24 22:54:59
|
John Clark wrote: > Paolo schrieb: > >> well, I do agree with Thorsten: seems nobody gets it right talking about >> Sam <-> HAL code... > > > I don't know, I've beein using Madwifi for 'over 2 years', and have > seen Sam Leffler's name since > forever, and never had a need to connect him to 'the HAL', other than > perhaps a query such > as 'is anyone working on X', any more than I've seen a need to > buttonhole him on 'BSD', of > any flavor... My mistake, I should have known better. It's just that I've been reading hal/ah.h, hal/ah_desc.h, hal/ah_devid.h and hal/README a lot lately and every time I open one of these files a copyright by Sam Leffler stares at me. Yes, I understand, the fact that he has his copyright on the header files does not mean he wrote the code that goes with these header files. It just creates a connection in my mind... TvE |
From: Michael R. <ma...@no...> - 2005-10-25 05:45:57
|
> hehe, i think we should put that in the HAL FAQ ;) Done. Bye, Mike |
From: coderman <cod...@gm...> - 2005-10-24 20:35:35
|
On 10/24/05, Rob Prowel <pr...@ku...> wrote: > ... I'm left with trying to figure out how to make it work in our 100% > open source environment. support http://ath-driver.org/ and start submitting patches. (more than a little code needs to be added for your purposes, have fun) |
From: John B. <jby...@ya...> - 2005-10-25 22:47:10
|
Is there somewhere I can learn to create patches? Maybe a link on the internet? Man page? Curiously, John John Byrne Software Engineer and Systems Administrator WebSpring > -----Original Message----- > From: mad...@li... [mailto:madwifi-users- > ad...@li...] On Behalf Of coderman > Sent: Monday, October 24, 2005 1:35 PM > To: Rob Prowel > Cc: mad...@li... > Subject: Re: [Madwifi-users] binary only HAL causes me EXTREME grief! > > On 10/24/05, Rob Prowel <pr...@ku...> wrote: > > ... I'm left with trying to figure out how to make it work in our 100% > > open source environment. > > support http://ath-driver.org/ and start submitting patches. (more > than a little code needs to be added for your purposes, have fun) > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users |
From: Cedric B. <bla...@ca...> - 2005-10-26 07:11:59
|
Le mardi 25 octobre 2005 =E0 15:46 -0700, John Byrne a =E9crit : > Is there somewhere I can learn to create patches? Maybe a link on the > internet? Man page? man 1 diff Simple way: diff -u <original_tree> <new_tree> --=20 http://sid.rstack.org/ PGP KeyID: 157E98EE FingerPrint: FA62226DA9E72FA8AECAA240008B480E157E98EE >> Hi! I'm your friendly neighbourhood signature virus. >> Copy me to your signature file and help me spread! |
From: Bob B. <bob...@gm...> - 2005-10-26 11:40:03
|
> > Is there somewhere I can learn to create patches? Maybe a link on the > > internet? Man page? > > man 1 diff see also, in your kernel sources, /usr/src/linux/Documentation/SubmittingPatches -- -Bob |
From: Matt F. <mat...@cl...> - 2005-10-26 08:08:02
|
Quoting John Byrne (jby...@ya...): > Is there somewhere I can learn to create patches? Maybe a link on the=20 > internet? Man page? >=20 I always use Mike's description here: http://madwifi.sourceforge.net/ (and now here: http://madwifi.org/wiki/Contribute).=20 Anyway, the man page you want is: man 1 diff=20 Hope this helps. --=20 Cheers, Matt Foster <mat...@cl...> ------------------------------------ NP: Martin Grech - Worldly Divine (Unholy) |
From: Andrew D. <at...@ed...> - 2005-10-24 22:54:35
|
> One of the specs that I wholeheartedly agree with is that no proprietar= y > (binary only) software will be used on the robot. All software must be > compiled and tested directly on the exact PPC that exists in the robot. > Well, apparently the previous engineer didn't read up on the binary onl= y > nature of parts of the atheros driver before choosing the chip and > selling the concept to management. > > So, I'm left with trying to figure out how to make it work in our 100% > open source environment. > > Who maintains the binary only HAL portion of the driver? > > What do I need to do to get ahold of the HAL code in source format? > > Has it been compiled on non-intel platforms (specifically linux 2.4.x > with the freescale5200 CPU?) > > Do I need to look at a different chip? which one? > > my specs that will not change are: > V2.4 linux > open source (security procedures mandate this) > PPC platform driver When you mean "security procedures", do you mean security procedures that you have chosen (possibly with some idealism involved in that choice), or that one of your company's clients has chosen (example: if you are workin= g for a defense contractor)? Keep in mind that as others have pointed out, there are NO 100% open-source WLAN options. Either you have a closed-source HAL (Atheros), or you have closed-source firmware that is either flashed to the chipset (Prism, Orinoco) or uploaded at driver load time (Intel Centrino, possibl= y others? Actually Prism2s support this in addition to permanent firmware flashing from what I remember). Admittedly, the Atheros HAL is slightly less optimal of a solution than firmware loaded onto the card, since the firmware is independent of host architecture and the HAL is. On the other hand, the HAL maintainer has been doing a very good job of keeping it ported to other architectures.=20 This difference is irrelevant in your situation if security is your reasoning for having HAL source access. There is no way you'll be able to use an open-source Atheros HAL, at leas= t in the OSI definitions of open-source. FCC regulations and Atheros polic= y simply will not allow it. Now if you simply need the source of the HAL for security vetting, then there is a chance you might be able to obtain it from Atheros for a fee.=20 If your security procedures are government-imposed, I would not be surprised if that will make it easier to obtain sources from Atheros. That said, complaining to this mailing list is probably not the best way to get access to the HAL source. It is probably better if your company approaches Atheros directly to negotiate some arrangement. |
From: Jim T. <ji...@ne...> - 2005-10-24 23:57:31
|
On Oct 24, 2005, at 12:54 PM, Andrew Dodd wrote: > > >> One of the specs that I wholeheartedly agree with is that no >> proprietary >> (binary only) software will be used on the robot. All software >> must be >> compiled and tested directly on the exact PPC that exists in the >> robot. This is silly. What makes you think you have any better security by running the compiler on an embedded part, than running a cross-compiler? >> Well, apparently the previous engineer didn't read up on the >> binary only >> nature of parts of the atheros driver before choosing the chip and >> selling the concept to management. All engineering is compromise. >> So, I'm left with trying to figure out how to make it work in our >> 100% >> open source environment. >> >> Who maintains the binary only HAL portion of the driver? >> >> What do I need to do to get ahold of the HAL code in source format? >> >> Has it been compiled on non-intel platforms (specifically linux 2.4.x >> with the freescale5200 CPU?) >> >> Do I need to look at a different chip? which one? >> >> my specs that will not change are: >> V2.4 linux >> open source (security procedures mandate this) >> PPC platform driver >> > > When you mean "security procedures", do you mean security > procedures that > you have chosen (possibly with some idealism involved in that > choice), or > that one of your company's clients has chosen (example: if you are > working > for a defense contractor)? > > Keep in mind that as others have pointed out, there are NO 100% > open-source WLAN options. Either you have a closed-source HAL > (Atheros), > or you have closed-source firmware that is either flashed to the > chipset > (Prism, Orinoco) or uploaded at driver load time (Intel Centrino, > possibly > others? Actually Prism2s support this in addition to permanent > firmware > flashing from what I remember). Actually, there are a couple. The raylink driver (on FreeBSD) has no binary portions and the rtl8181/8180 driver (on sourceforge) is also 100% Free Software (GPL). > > Admittedly, the Atheros HAL is slightly less optimal of a solution > than > firmware loaded onto the card, since the firmware is independent of > host > architecture and the HAL is. Strictly your POV. > On the other hand, the HAL maintainer has > been doing a very good job of keeping it ported to other > architectures. And gets nothing but arrows in the back for his efforts. > This difference is irrelevant in your situation if security is your > reasoning for having HAL source access. > > There is no way you'll be able to use an open-source Atheros HAL, > at least > in the OSI definitions of open-source. FCC regulations and Atheros > policy > simply will not allow it. > > Now if you simply need the source of the HAL for security vetting, > then > there is a chance you might be able to obtain it from Atheros for a > fee. > If your security procedures are government-imposed, I would not be > surprised if that will make it easier to obtain sources from Atheros. > > That said, complaining to this mailing list is probably not the > best way > to get access to the HAL source. It is probably better if your > company > approaches Atheros directly to negotiate some arrangement. Atheros has programs in-place for this type of activity. You may be able to approach an ADC to do the security audit for you. Else, if you represent a large enough opportunity for Atheros, then you may get to sign the "technology license agreement" and get your very own copy of the HAL source code. See your Atheros salesperson for further details. Jim |