... because some of the 802.11p NICs are actually ath5k NICs that have the relevant bandpass filters for 5.9GHz and high output amplifiers.
-a On 17 February 2014 01:27, Holger Schurig <holgerschu...@gmail.com> wrote: > Okay, I admit that I cannot help you, I have no clue on the driver level. > > But maybe I can help with the methodology. :-) > > You mention 802.11p (car-to-car-communication). Is there any specific > reason you base it on ath5k and not on ath9k? If you look at the > number of commits, then you should see that ath9k is much more lively. > People are actively working with that code and might be able to be > answer more specific questions. > Another thing that I noted: I have seen over the years many requests > of information from uni projects in this mailing list. But I'm quite > unsure if ever something came back into the Linux kernel. How do you > plan to tackle that? I have the feeling that people are more likely > to cooperate if the work doesn't end up in yet another black hole ... > > And one tip: ask specific questions, not broad ones. For example, look > at what features you need to implement 802.11p. Now look at what OSI > level this has to be done, e.g. at hardware level (frequency, > bandwidth), driver level, or protocoll layer (mac80211, user-space > layer (e.g. wpa_supplicant). That would allow you to ask questions not > like "Tell me everything", but "Oh, I need to do XYZ, where can I do > it?". It might even help you in finding your way, e.g. by looking into > git commits inside the ath/ath9k subdirectories that might have > something to do with what you need. > _______________________________________________ > ath5k-devel mailing list > ath5k-devel@lists.ath5k.org > https://lists.ath5k.org/mailman/listinfo/ath5k-devel _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
