From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from optimeas.de ([78.46.18.2]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1ToFoc-0000oU-BY for ptxdist@pengutronix.de; Thu, 27 Dec 2012 16:56:16 +0100 Received: from [192.168.178.22] (krlh-d9be63eb.pool.mediaWays.net [217.190.99.235]) by optimeas.de (Postfix) with ESMTPSA id 069584207A56 for ; Thu, 27 Dec 2012 16:56:08 +0100 (CET) From: "Dr. Patrick Langfeld" Date: Thu, 27 Dec 2012 15:56:10 +0000 Message-Id: Mime-Version: 1.0 Subject: [ptxdist] Fw: Re: Crosscompile a WIFI USB stick firmware with ptxdist Reply-To: ptxdist@pengutronix.de, "Dr. Patrick Langfeld" List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: "ptxdist@pengutronix.de" Dear Thomas, please call me Patrick :-) Thank you very much for your quick response! I cant believe that it should be that simple - that would be really good news :-). (as my developer experience is that things are almost always more complicated than expected) You mean it might be sufficient to copy the carl9170-1.fw to my targets destination /usr/local/lib/firmware eg. mkdir /usr/local/lib/firmware mv carl9170-1.fw /usr/local/lib/firmware Am I right? Is there a way that ptxdist can care for that to automize the job? OK, I will have a look at the "4.3 Adding binary only files" chapter, page 45 of the "how to become a ptxdist guru" pdf. I think thats the one. What I will also need are the packages for "wireless-tools" and "wpasupplicant". in the userland (./ptx menuconfig) I already found the packages in Networking Tools (cool) <*> wireless tools <*> wpa_supplicant The latter has some subpackages [ ] dbus control interface [ ] AP mode [ ] P2P [ ] hostap [ ] wext [ ] ralink [ ] nl80211 [ ] wired [ ] roboswitch [*] Install wpa_cli Any idea what I will need as a minimum? Of course you will say that depends on what I want to do ;-) I want a) my device to be a client and connecting with an access point and alternative b) a P2P connection with a PC (or multiple devices, each of them with a P2P connection to a dedicated PC). Best regards Patrick ------ Weitergeleitete Nachricht ------ Von: "Thomas Petazzoni" An: ptxdist@pengutronix.de; "Dr. Patrick Langfeld" Gesendet: 27.12.2012 15:01:40 Betreff: Re: [ptxdist] Crosscompile a WIFI USB stick firmware with ptxdist Dear Dr. Patrick Langfeld, On Thu, 27 Dec 2012 13:12:28 +0000, Dr. Patrick Langfeld wrote: > My kernel is already configured with the wireless LAN components for > 80211 and the driver in Lan USB network adapter using the CARL9170, > which is the correct one for the DWA-160. > > Now the hard part is to crosscompile the firmware carl9170-1.fw for >the > USB network adapter. The sources can be found in a git repository > https://github.com/chunkeey/carl9170fw.git If you don't intend to do active development on this firmware, it's probably easier to use a pre-built version of it, as available at http://linuxwireless.org/en/users/Drivers/carl9170#Firmware_binary. > and come with an autogen.sh script file, which I attached for you to > have a look at. > > Now I am wondering HOW TO PROCEED and implement the build process of > autogen.sh in ptxdist and which package type is appropriate. Is it a > ./ptx newpackage target or a src-cmake-prog as the autogen.sh makes >use > of cmake. > In the readme file is written, that to build the firmware one would >need > a SH-2 toolchain. Is this also true for cross-compilation? Do I really > need to build this toolchain first? The firmware is the code that runs *inside* your Wifi chip, and apparently this Wifi chip uses a SuperH 2 processor. So, regardless of whether your embedded system uses a ARM processor, a x86 processor, or something else, your USB Wifi device embeds a SH2 processor, and the firmware is targeting this processor, not your main application processor (ARM i.MX53 in your case). So again, unless you need to make modifications to the firmware, I would probably recommend to go with a pre-built version. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- ptxdist mailing list ptxdist@pengutronix.de