From: Curtis O. <cur...@fl...> - 2012-10-01 14:44:38
|
On Fri, Sep 28, 2012 at 8:00 AM, jumpnowdev <sc...@ju...> wrote: > Donny3000's patches eariler in this thread fixed the slow bring up problem > for me. > > Same issue you report, 40 seconds until the libertas firmware loads. > > Thanks Donald! > > I'm using it with Sakoman's 3.2 kernel. > > I consolidated the patches into one file here > > > https://github.com/scottellis/meta-jumpnow/blob/master/recipes-kernel/linux/linux-sakoman-3.2/libertas-async-fwload.patch > > and an example on how to include it in the kernel recipe here > > > https://github.com/scottellis/meta-jumpnow/blob/master/recipes-kernel/linux/linux-sakoman_3.2.bb > > I have nothing related to the wifi drivers in /etc/modprobe.d > I've started looking around for info on running the 3.2 kernel with the sakoman r13 system and I don't see much (or maybe nothing) on the sakoman site about this. I can't find any packages in opkg list that relate to the 3.2 kernel. Are there any instructions posted somewhere that I'm missing? I see bits and blurbs about compiling a 3.2 kernel in the mailing list archives when I google, but it's been longer than 6 months since I've tried to build the linux kernel so I've forgotten most of what I knew about that. Most of what I've found is references to people getting 3.2 running or trying to, but nothing about how to do it? Are there any instructions posted anywhere for getting the 3.2 kernel going on a sakoman r13 system? Thanks, Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org |
From: Curtis O. <cur...@fl...> - 2012-10-01 21:44:55
|
Since there hasn't been any replies to my specific question, maybe I can re-ask a slightly different way? I have a usb wifi device I'd like to run from my overo. It works on my fedora desktop system. However, the drivers are not built by default in the sakoman r13 v3.0.0 kernel. I need the ath9k_htc drivers. I think I see a reference to those in the 3.0.0 kernel config. I think (I hope!) the drivers are included in the 3.0.0 kernel or the 3.2 kernel so at this point I don't care either way which one I use, but I'd like to rebuild the kernel with the needed drivers included, or build just the driver modules I need (?) In the old default gumstix OpenEmbedded system with bitbake, I was able to rebuild the kernel 2.6 and had that figured out, but that was quite a while ago now. What do I need to do to rebuild the kernel (or just the modules I need) in the sakoman system? Are there any short cuts or docs? Do I need to start from scratch and recompile the entire sakoman r13 + gnome distribution from source? Is there a way to streamline that and just build the kernel and not the whole rootfs from source? Can I do this with the native development system onboard the overo or do I need to cross compile from my linux pc host? I run Fedora here. Most of the "from scratch" instructions presume Ubuntu -- is that a requirement for doing any or all of this? I can probably figure out quite a bit on my own, but I'm hoping someone can just nudge me in the right starting direction here and tell me that the shortest path to building a new kernel for sakoman r13 is to do XYZ, and hopefully I can take it from there with minimal hand holding. I'd like to avoid having to compile the entire shooting match from scratch if I can, but if I must, then maybe someone can at least tell me that so I don't waste time looking for shortcuts that don't exist? Thanks! (And I apologize in advance if these are dumb questions and I've just missed all the documentation -- but in that case please could someone point me to the appropriate documentation?) Curt. On Mon, Oct 1, 2012 at 9:44 AM, Curtis Olson <cur...@fl...>wrote: > I've started looking around for info on running the 3.2 kernel with the > sakoman r13 system and I don't see much (or maybe nothing) on the sakoman > site about this. I can't find any packages in opkg list that relate to the > 3.2 kernel. Are there any instructions posted somewhere that I'm missing? > > I see bits and blurbs about compiling a 3.2 kernel in the mailing list > archives when I google, but it's been longer than 6 months since I've tried > to build the linux kernel so I've forgotten most of what I knew about that. > Most of what I've found is references to people getting 3.2 running or > trying to, but nothing about how to do it? > > Are there any instructions posted anywhere for getting the 3.2 kernel > going on a sakoman r13 system? > > Thanks, > > Curt. > -- > Curtis Olson: > http://www.atiak.com - http://aem.umn.edu/~uav/ > http://www.flightgear.org - http://gallinazo.flightgear.org > > -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org |
From: Donny3000 <don...@sw...> - 2012-10-02 14:05:17
|
Hello Curtis, Sorry for the delay, but I have been tied up with another project for the past few months. I will try to answer you questions the best I can. * > In the old default gumstix OpenEmbedded system with bitbake, I was able to > rebuild the kernel 2.6 and had that figured out, but that was quite a > while ago now. > > What do I need to do to rebuild the kernel (or just the modules I need) in > the sakoman system? Are there any short cuts or docs? * What I usually do is run the bitbake command /bitbake -c menuconfig virtual/kernel/ to configure the kernel that way I need it and then run /bitbake virtual/kernel/ to rebuild the kernel (you might have to clean the kernel first with bit bake -c clean virtual/kernel and then configure/build the kernel, but I can't recall). * > Do I need to start from scratch and recompile the entire sakoman r13 + > gnome distribution from source? * I'm not familiar with building the sakoman distributions so I can't confirm or deny this. But, I presume their should be a way to either install the newly compiled kernel built with OpenEmbedded or just install the LKM itself if the kernel configured/built with OpenEmbedded is the same as the kernel running on the r13+ sakoman distribution you are using. * > Is there a way to streamline that and just build the kernel and not the > whole rootfs from source? * My first answer should allow you to just build the kernel and not the whole rootfs. * > Can I do this with the native development system onboard the overo or do I > need to cross compile from my linux pc host? * You could do this on the Overo if you have the build tools necessary, but I will probably take the whole day (probably more) to recompile the kernel. Your best bet is to cross-compile the kernel and either install it manually or use the opkg package manager on the overo. * > I run Fedora here. Most of the "from scratch" instructions presume Ubuntu > -- is that a requirement for doing any or all of this? * It's highly recommended, but I'm sure you can use Fedora with the right workarounds/modifications. I think a few members of the community here use Fedora as well, so you will have to ask around to see how they configured there system accordingly. * > I can probably figure out quite a bit on my own, but I'm hoping someone > can just nudge me in the right starting direction here and tell me that > the shortest path to building a new kernel for sakoman r13 is to do XYZ, > and hopefully I can take it from there with minimal hand holding. I'd > like to avoid having to compile the entire shooting match from scratch if > I can, but if I must, then maybe someone can at least tell me that so I > don't waste time looking for shortcuts that don't exist? * Again, I'm not the best source for the Sakoman images (may be Steve will chime in here and give some insight), but I really don't think you need to rebuild the entire distribution just to update the kernel or add a few LKMs to your currently running kernel. I hope $0.02 will help get you started and pointing you in the right direction. -Donald -- View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4965540.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: kris d. <t_...@ya...> - 2012-10-17 19:31:14
|
Hello, I work with overo for some time and would like to switch to duovero. I have looked in the documentation to see how to get started, which branch to checkout and how to create the image since there is no nand on the COM. with the overo COM, I used the documentation found here : http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html to create my environment. I have found nothing for the duovero. I found that the kernel to use is the 3.6, and found that we now need to use the yocto project ?! No more open embedded ? With open embedded it was possible to compile on the gumstix, is it possible with the duovero ? So, here are my questions : 1. is there any documentation to get started with the duovero ? 2. is it possible to compile on the duovero COM ? Thank you :-) Kris |
From: kris d. <t_...@ya...> - 2012-10-17 23:48:44
|
Hello For a custom application, I need to have 3mm between boards. Unfortunately at gumstix the spacers are 1.5mm. Does somebody knows which company produce these small pieces ? I have found some replacements but the smaller part needs a 4mm hole, not a #0-80 as for the gumstix. Thank you Kris |
From: Ash C. <as...@gu...> - 2012-10-19 16:23:06
|
Hi Kris, > with the overo COM, I used the documentation found here : > http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html > to create my environment. I have found nothing for the duovero. There is woefully little about the development environment at this point but the primary focus has been on getting a kernel that works well with the duoVero: http://gumstix.org/access-source-code.html At this point, I'd recommend DuoVero COMs for those who are comfortable adding their own meta-layer to a oe-core build for DuoVero or those who specifically want the OMAP4430. Better software support is underway! > > I found that the kernel to use is the 3.6, and found that we now need to use > the yocto project ?! No more open embedded ? The Yocto Project is an umbrella project that includes OE. A lot of the technology is the same between oe-classic and the oe-core+meta-layers version currently in use. > > With open embedded it was possible to compile on the gumstix, is it possible > with the duovero ? Yes---native compilation works on DuoVero too. > > So, here are my questions : > > 1. is there any documentation to get started with the duovero ? For the hardware guys, this is the best source so far: http://gumstix.org/images/duovero_srm_latest.pdf > 2. is it possible to compile on the duovero COM ? It is definitely possible to compile on the duoVero COM. --Ash |
From: kris d. <t_...@ya...> - 2012-10-25 01:56:30
|
Hello Ash, Thank you for your reply, Now I am convinced that I will stay with the overo line :-) I appreciate ! Kris ________________________________ From: Ash Charles <as...@gu...> To: kris duff <t_...@ya...>; General mailing list for gumstix users. <gum...@li...> Sent: Friday, October 19, 2012 12:22:27 PM Subject: Re: [Gumstix-users] duovero getting started ? Hi Kris, > with the overo COM, I used the documentation found here : > http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html > to create my environment. I have found nothing for the duovero. There is woefully little about the development environment at this point but the primary focus has been on getting a kernel that works well with the duoVero: http://gumstix.org/access-source-code.html At this point, I'd recommend DuoVero COMs for those who are comfortable adding their own meta-layer to a oe-core build for DuoVero or those who specifically want the OMAP4430. Better software support is underway! > > I found that the kernel to use is the 3.6, and found that we now need to use > the yocto project ?! No more open embedded ? The Yocto Project is an umbrella project that includes OE. A lot of the technology is the same between oe-classic and the oe-core+meta-layers version currently in use. > > With open embedded it was possible to compile on the gumstix, is it possible > with the duovero ? Yes---native compilation works on DuoVero too. > > So, here are my questions : > > 1. is there any documentation to get started with the duovero ? For the hardware guys, this is the best source so far: http://gumstix.org/images/duovero_srm_latest.pdf > 2. is it possible to compile on the duovero COM ? It is definitely possible to compile on the duoVero COM. --Ash |