Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-09 Thread Matt Maher Peterson
Thanks that worked to adafruit library working. Still having an issues getting the device tree to load on boot. Is there a better way to do this than in /boot/uEnv.txt ? I have this line in there now but it does not seam to do the job as I do not see the overlay loaded after boot in

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-09 Thread Matt Maher Peterson
Ah k. lol that makessense now. Have that done but still not loading my overlay on boot... On Wednesday, December 9, 2015 at 11:52:21 AM UTC-8, William Hermans wrote: > > In other words. if the file */usr/share/initramfs-tools/hooks/dtbo *is > not already executable run chmod +x on it. *OR* You

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-09 Thread William Hermans
> > > > *Now do I add this to the file?* > > > > *if [ ! -x /usr/share/initramfs-tools/hooks/dtbo ] ; then sudo chmod > +x /usr/share/initramfs-tools/hooks/dtbo fi * > That's bash script programmer speak for making that file executable, if it's not already ;) On Wed, Dec 9, 2015 at 10:13

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-09 Thread William Hermans
In other words. if the file */usr/share/initramfs-tools/hooks/dtbo *is not already executable run chmod +x on it. *OR* You could create a bash script, drop that code into it. Make the script executable, then run it. And it'd do it for you. Pick your poison. On Wed, Dec 9, 2015 at 12:48 PM,

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-09 Thread Robert Nelson
On Wed, Dec 9, 2015 at 10:42 AM, Matt Maher Peterson wrote: > Thanks that worked to adafruit library working. > > > Still having an issues getting the device tree to load on boot. > > Is there a better way to do this than in /boot/uEnv.txt ? I have this line >

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-09 Thread Matt Maher Peterson
Thanks for bearing with me here. I did a wget https://github.com/rcn-ee/repos/blob/master/bb-bb-customizations/suite/jessie/debian/dtbo

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-08 Thread Matt Maher Peterson
OK so I upgraded to 4.1.13.ti.r35 How do I use this rebuilder? Just to confirm I have a custom .dtbo name BB-APA-01 that loaded on boot where I had it baked into the kernel. I did not add it uEnv.txt but it still loaded. Here is what I tried to get cape loaded: root@mmpTestBox:~# dmesg |

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-08 Thread Matt Maher Peterson
How do I apply this patch? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-08 Thread Robert Nelson
On Tue, Dec 8, 2015 at 6:50 PM, Matt Maher Peterson wrote: > How do I apply this patch? git clone https://github.com/adafruit/adafruit-beaglebone-io-python cd ./adafruit-beaglebone-io-python wget

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-08 Thread Matt Maher Peterson
How do I apply this patch? Matt Maher Peterson APANA w: 360.746.2276x401 c: 360.393.5549 On Tue, Dec 8, 2015 at 4:45 PM, Robert Nelson wrote: > On Tue, Dec 8, 2015 at 6:01 PM, Matt Maher Peterson > wrote: > > So I was able to to get

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-08 Thread Matt Maher Peterson
So I was able to to get the custom dtbo loaded after recompiling it with: dtc -O dtb -o BB-APA-01-00A0.dtbo -b 0 -@ BB-APA-02-00A0.dts Did the UARTS get renamed? I also had to remove this from the dts to get it to comiple: fragment@4 { target = <>;

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-08 Thread Robert Nelson
On Tue, Dec 8, 2015 at 6:01 PM, Matt Maher Peterson wrote: > So I was able to to get the custom dtbo loaded after recompiling it with: > > dtc -O dtb -o BB-APA-01-00A0.dtbo -b 0 -@ BB-APA-02-00A0.dts > > Did the UARTS get renamed? I also had to remove this from

[beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson
Hi, Working with a Telit LE910 Cell Module and am trying to get a driver working for usb connection. I am following the guide provided by Telit I have loaded the kernel headers and such so that I

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Robert Nelson
On Mon, Dec 7, 2015 at 5:07 PM, Matt Maher Peterson < matt.maherpeter...@hydro-care.com> wrote: > Hi, > > Working with a Telit LE910 Cell Module and am trying to get a driver > working for usb connection. > > I am following the guide provided by Telit >

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson
Thanks for the clarification Rpbert What is the proper way to 'retrieve the appropriate kernel source code..." for 3.18.3-bone70? Matt Maher Peterson APANA w: 360.746.2276x401 c: 360.393.5549 On Mon, Dec 7, 2015 at 3:10 PM, Robert Nelson wrote: > > > On Mon, Dec 7,

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson
Thanks for the clarification Rpbert What is the proper way to 'retrieve the appropriate kernel source code..." for 3.18.3-bone70? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Robert Nelson
On Mon, Dec 7, 2015 at 5:13 PM, Matt Maher Peterson wrote: > Thanks for the clarification Rpbert > > > What is the proper way to 'retrieve the appropriate kernel source code..." > for 3.18.3-bone70? > git clone https://github.com/RobertCNelson/linux-stable-rcn-ee cd

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Robert Nelson
On Mon, Dec 7, 2015 at 6:15 PM, Matt Maher Peterson wrote: > Thanks Robert. > > I found the file and everything seams legit. The real issue I was trying to > solve was that when plugging this device in to the USB input I was not > getting the corresponding

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson
Thanks Robert. I found the file and everything seams legit. The real issue I was trying to solve was that when plugging this device in to the USB input I was not getting the corresponding /dev/USBX's. After doing a modprobe option echo 1bc7 1201 > /sys/bus/usb-serial/drivers/option1/new_id I

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson
Yes I could but I have a custom device tree written to work in the old world of 3.18.3 Is there a simple way to port that into 4.1.13.ti.r35 ? On Monday, December 7, 2015 at 4:19:49 PM UTC-8, RobertCNelson wrote: > > On Mon, Dec 7, 2015 at 6:15 PM, Matt Maher Peterson >

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread William Hermans
There is no porting. You simply compile it with the proper device tree version. Which is different from the version used for 3.8.x. http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/ On Mon, Dec 7, 2015 at 5:21 PM, Matt Maher Peterson <

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Robert Nelson
On Mon, Dec 7, 2015 at 6:21 PM, Matt Maher Peterson wrote: > Yes I could but I have a custom device tree written to work in the old world > of 3.18.3 Is there a simple way to port that into 4.1.13.ti.r35 ? Yeap, two options, install 4.1.13.ti.r35 Then use the

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread William Hermans
Anyway, if you apt-get install linux-image, and it ends up not working for you, simply change the uname-r variable in /boot/uEnv.txt ( to point to your 3.8.x kernel ). And problem solved. After that, an apt-get remove --purge should get rid of all traces of the newer 4.1.x kernel. *IF* that's