X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] OT: wifi (802.11) embedded implementation
To:	geda-user AT delorie DOT com
References:	<b4007158-ec3c-b843-79ec-53f9647c751f AT iae DOT nl>
From:	"John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<6f0a0188-fb2d-3325-5abd-5b29b17a910c@ecosensory.com>
Date:	Thu, 31 Aug 2017 20:51:14 -0500
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
	Thunderbird/52.2.1
MIME-Version:	1.0
In-Reply-To:	<b4007158-ec3c-b843-79ec-53f9647c751f@iae.nl>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 08/31/2017 04:16 PM, myken wrote:
> I would like to implement a wifi connection on an embedded application using the applications own MPU + an additional MAC/PHY.
> Is this a very silly thing to do? Because after a day of searching I have found a lot of ready to use wifi-modules but almost no 
> separate MPU-MAC/PHY solutions.
> Has anyone done this? Am I missing something why this approach is just not done (besides the SW-stack needed)?

No, it is mostly done with a sw stack or some overall system like riot OS or lwip.
The latest is an Asian wonder the esp8266 or esp32 chips with code inside...for $1 or $2 or 60 cents if you get bare chips
and make a board yourself.

The wireless code takes lots of work to customize or create, or lots of money to exclusively license any, so that's why you see so 
little offered.   There was a FOSS code called TinyOS that I worked with some and it just fizzled out.  That was 802.15.4, not 
802.11, but same center frequency.

- Raw text -