Re: [SailfishDevel] No QSerialPort
Hi Philippe From this and other threads going back to the very early days of this mailing list it is very clear that Wim wants to connect an external GPS unit to his Jolla via cable (usb / serial) for use in the cockpit of a glider. HtH Chris Zitat von "Philippe De Swert" : Hi, As this is getting very confused and we are mixing connecting devices to the Jolla and connecting the Jolla to the pc. So which one is it? On 26/03/14 22:11, Wim de Vries wrote: Thank you guys. Indeed devel-su works. I have attached the devices, but the first problem is that the connection does not supply power (the devices stay dead). So you connected some device to your Jolla? As far as I know, a usb connection should always have power, but it is a bit beyond my kowledge. Do I need another plug? This is not true. All depends on context, what you plug into what etc... In general if you plug in a device into a USB host (like your average USB port on your pc/laptop) you should be able to expect power from it. In the case of a phone this is usually a USB device, so it expects power. And in the OTG case it gets complicated. Here the device is able to switch between host and device mode. And will supply power if it is playing host. On other linux/MeeGo systems there was always power... and dmesg would give: [ 31.959468] usb 3-2.1.4: new full-speed USB device number 7 using xhci_hcd [ 31.977423] usb 3-2.1.4: New USB device found, idVendor=10c4, idProduct=ea60 [ 31.977434] usb 3-2.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 31.977440] usb 3-2.1.4: Product: CP2102 USB to UART Bridge Controller [ 31.977445] usb 3-2.1.4: Manufacturer: Silicon Labs [ 31.977450] usb 3-2.1.4: SerialNumber: 0001 [ 31.992330] usbcore: registered new interface driver usbserial [ 31.992343] usbcore: registered new interface driver usbserial_generic [ 31.992355] USB Serial support registered for generic [ 31.992361] usbserial: USB Serial Driver core [ 31.992942] usbcore: registered new interface driver cp210x [ 31.992955] USB Serial support registered for cp210x [ 31.992991] cp210x 3-2.1.4:1.0: cp210x converter detected [ 32.063473] usb 3-2.1.4: reset full-speed USB device number 7 using xhci_hcd [ 32.079934] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801debc38c0 [ 32.079947] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801debc3880 [ 32.080450] usb 3-2.1.4: cp210x converter now attached to ttyUSB0 Use Qserialport on ttyUSB0 and ready you are. This looks like plugging in a serial device into a PC. Do you want your Jolla to expose a serial port? That is definitely possible and easy. Do you want your Jolla to read data from some serial port with a serial to USB adapter then you're getting in a very complicated world. Unless you can explain what you actually want there is little we can do to help. Regards, Philippe ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No QSerialPort
On Thursday, March 27, 2014 03:10:29 AM Ove Kåven wrote: > The OP (wsvries) has always talked about connecting the Jolla to a USB > device, never about connecting it to a PC (only about connecting those > USB devices to a PC, not the Jolla). Then, for no reason, Radek started > talking about connecting the Jolla to a PC, and a couple of others > followed suit. Hi, sorry for confusion - i didnt read carefully. Regards Radek ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No QSerialPort
Den 27. mars 2014 00:39, skrev Philippe De Swert: Hi, As this is getting very confused and we are mixing connecting devices to the Jolla and connecting the Jolla to the pc. So which one is it? Personally I don't see why there's any confusion. The OP (wsvries) has always talked about connecting the Jolla to a USB device, never about connecting it to a PC (only about connecting those USB devices to a PC, not the Jolla). Then, for no reason, Radek started talking about connecting the Jolla to a PC, and a couple of others followed suit. On the other hand, wsvries apparently did not understand the message when he was told that USG OTG is not supported. He didn't seem to get that it really *means* that it isn't supported, and thus that this isn't going to work and the Jolla isn't going to supply power, and kept forging ahead anyway (and apparently got surprised when it didn't supply power). It's actually fascinating, from where I'm standing. Anyway, yes, probably an externally-powered USB hub (or, perhaps more elegantly, the TOH i2c connections) are the only hopes of achieving what he wants to do. ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No QSerialPort
Hi, As this is getting very confused and we are mixing connecting devices to the Jolla and connecting the Jolla to the pc. So which one is it? On 26/03/14 22:11, Wim de Vries wrote: Thank you guys. Indeed devel-su works. I have attached the devices, but the first problem is that the connection does not supply power (the devices stay dead). So you connected some device to your Jolla? As far as I know, a usb connection should always have power, but it is a bit beyond my kowledge. Do I need another plug? This is not true. All depends on context, what you plug into what etc... In general if you plug in a device into a USB host (like your average USB port on your pc/laptop) you should be able to expect power from it. In the case of a phone this is usually a USB device, so it expects power. And in the OTG case it gets complicated. Here the device is able to switch between host and device mode. And will supply power if it is playing host. On other linux/MeeGo systems there was always power... and dmesg would give: [ 31.959468] usb 3-2.1.4: new full-speed USB device number 7 using xhci_hcd [ 31.977423] usb 3-2.1.4: New USB device found, idVendor=10c4, idProduct=ea60 [ 31.977434] usb 3-2.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 31.977440] usb 3-2.1.4: Product: CP2102 USB to UART Bridge Controller [ 31.977445] usb 3-2.1.4: Manufacturer: Silicon Labs [ 31.977450] usb 3-2.1.4: SerialNumber: 0001 [ 31.992330] usbcore: registered new interface driver usbserial [ 31.992343] usbcore: registered new interface driver usbserial_generic [ 31.992355] USB Serial support registered for generic [ 31.992361] usbserial: USB Serial Driver core [ 31.992942] usbcore: registered new interface driver cp210x [ 31.992955] USB Serial support registered for cp210x [ 31.992991] cp210x 3-2.1.4:1.0: cp210x converter detected [ 32.063473] usb 3-2.1.4: reset full-speed USB device number 7 using xhci_hcd [ 32.079934] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801debc38c0 [ 32.079947] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801debc3880 [ 32.080450] usb 3-2.1.4: cp210x converter now attached to ttyUSB0 Use Qserialport on ttyUSB0 and ready you are. This looks like plugging in a serial device into a PC. Do you want your Jolla to expose a serial port? That is definitely possible and easy. Do you want your Jolla to read data from some serial port with a serial to USB adapter then you're getting in a very complicated world. Unless you can explain what you actually want there is little we can do to help. Regards, Philippe ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No QSerialPort
https://together.jolla.com/question/50/why-its-not-possible-to-use-usb-otg/ So if you use external power (like powered usb hub or powered cable http://forum.xda-developers.com/showthread.php?t=1828032 ) , compile and install your own kernel modules and then you might get lucky. For that effort you might just want to build some custom i2c serial adapter TOH yourself. re, Jonni From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Wim de Vries [wsvr...@xs4all.nl] Sent: Wednesday, March 26, 2014 10:11 PM To: Sailfish OS Developers Subject: Re: [SailfishDevel] No QSerialPort Thank you guys. Indeed devel-su works. I have attached the devices, but the first problem is that the connection does not supply power (the devices stay dead). As far as I know, a usb connection should always have power, but it is a bit beyond my kowledge. Do I need another plug? On other linux/MeeGo systems there was always power... and dmesg would give: [ 31.959468] usb 3-2.1.4: new full-speed USB device number 7 using xhci_hcd [ 31.977423] usb 3-2.1.4: New USB device found, idVendor=10c4, idProduct=ea60 [ 31.977434] usb 3-2.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 31.977440] usb 3-2.1.4: Product: CP2102 USB to UART Bridge Controller [ 31.977445] usb 3-2.1.4: Manufacturer: Silicon Labs [ 31.977450] usb 3-2.1.4: SerialNumber: 0001 [ 31.992330] usbcore: registered new interface driver usbserial [ 31.992343] usbcore: registered new interface driver usbserial_generic [ 31.992355] USB Serial support registered for generic [ 31.992361] usbserial: USB Serial Driver core [ 31.992942] usbcore: registered new interface driver cp210x [ 31.992955] USB Serial support registered for cp210x [ 31.992991] cp210x 3-2.1.4:1.0: cp210x converter detected [ 32.063473] usb 3-2.1.4: reset full-speed USB device number 7 using xhci_hcd [ 32.079934] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801debc38c0 [ 32.079947] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801debc3880 [ 32.080450] usb 3-2.1.4: cp210x converter now attached to ttyUSB0 Use Qserialport on ttyUSB0 and ready you are. Nothing of this the dmesg of Jolla, though :-( r wim On 03/26/2014 12:34 PM, Jozef Mlich wrote: > On Wed, 2014-03-26 at 12:07 +0100, Wim de Vries wrote: >> On 03/26/2014 07:34 AM, Radek Polak wrote: >> >>> On Tuesday, March 25, 2014 12:32:34 PM wsvries wrote: >>> >>> >>> Don know about OTG, but my Linux systems always attach a Generic >>> Serial >>> Driver to the devices. Why is Sailfish acting differently? >>> >>> >>> No idea how this is in jolla but in openmoko there were options >>> while configuring linux kernel how the device will act when >>> connected to PC . IIRC it was somewhere in USB/gadget menu. You >>> could choose the device to act as USB mass storage, USB ethernet or >>> the USB serial devices. >>> >> I just tried it connecting and run dmesg in the terminal. >> Need root permission I guess ... >> But there is no sudo >> Any hints? >> Thanks. > As far a I know, mer/jolla have "devel-su" command which gives you root > permissions. > > ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No QSerialPort
Thank you guys. Indeed devel-su works. I have attached the devices, but the first problem is that the connection does not supply power (the devices stay dead). As far as I know, a usb connection should always have power, but it is a bit beyond my kowledge. Do I need another plug? On other linux/MeeGo systems there was always power... and dmesg would give: [ 31.959468] usb 3-2.1.4: new full-speed USB device number 7 using xhci_hcd [ 31.977423] usb 3-2.1.4: New USB device found, idVendor=10c4, idProduct=ea60 [ 31.977434] usb 3-2.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 31.977440] usb 3-2.1.4: Product: CP2102 USB to UART Bridge Controller [ 31.977445] usb 3-2.1.4: Manufacturer: Silicon Labs [ 31.977450] usb 3-2.1.4: SerialNumber: 0001 [ 31.992330] usbcore: registered new interface driver usbserial [ 31.992343] usbcore: registered new interface driver usbserial_generic [ 31.992355] USB Serial support registered for generic [ 31.992361] usbserial: USB Serial Driver core [ 31.992942] usbcore: registered new interface driver cp210x [ 31.992955] USB Serial support registered for cp210x [ 31.992991] cp210x 3-2.1.4:1.0: cp210x converter detected [ 32.063473] usb 3-2.1.4: reset full-speed USB device number 7 using xhci_hcd [ 32.079934] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801debc38c0 [ 32.079947] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801debc3880 [ 32.080450] usb 3-2.1.4: cp210x converter now attached to ttyUSB0 Use Qserialport on ttyUSB0 and ready you are. Nothing of this the dmesg of Jolla, though :-( r wim On 03/26/2014 12:34 PM, Jozef Mlich wrote: On Wed, 2014-03-26 at 12:07 +0100, Wim de Vries wrote: On 03/26/2014 07:34 AM, Radek Polak wrote: On Tuesday, March 25, 2014 12:32:34 PM wsvries wrote: Don know about OTG, but my Linux systems always attach a Generic Serial Driver to the devices. Why is Sailfish acting differently? No idea how this is in jolla but in openmoko there were options while configuring linux kernel how the device will act when connected to PC . IIRC it was somewhere in USB/gadget menu. You could choose the device to act as USB mass storage, USB ethernet or the USB serial devices. I just tried it connecting and run dmesg in the terminal. Need root permission I guess ... But there is no sudo Any hints? Thanks. As far a I know, mer/jolla have "devel-su" command which gives you root permissions. ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No QSerialPort
On Wed, 2014-03-26 at 12:07 +0100, Wim de Vries wrote: > On 03/26/2014 07:34 AM, Radek Polak wrote: > > > On Tuesday, March 25, 2014 12:32:34 PM wsvries wrote: > > > > > > > > > Don know about OTG, but my Linux systems always attach a Generic > > Serial > > > > > Driver to the devices. > > > > > Why is Sailfish acting differently? > > > > > > > > No idea how this is in jolla but in openmoko there were options > > while configuring linux kernel how the device will act when > > connected to PC . IIRC it was somewhere in USB/gadget menu. You > > could choose the device to act as USB mass storage, USB ethernet or > > the USB serial devices. > > > > I just tried it connecting and run dmesg in the terminal. > Need root permission I guess ... > But there is no sudo > Any hints? > Thanks. As far a I know, mer/jolla have "devel-su" command which gives you root permissions. -- Jozef Mlich ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No QSerialPort
there is sudo in mer-tools repo, i think 26.03.2014 17:07, Wim de Vries ?: On 03/26/2014 07:34 AM, Radek Polak wrote: On Tuesday, March 25, 2014 12:32:34 PM wsvries wrote: > Don know about OTG, but my Linux systems always attach a Generic Serial > Driver to the devices. > Why is Sailfish acting differently? No idea how this is in jolla but in openmoko there were options while configuring linux kernel how the device will act when connected to PC . IIRC it was somewhere in USB/gadget menu. You could choose the device to act as USB mass storage, USB ethernet or the USB serial devices. I just tried it connecting and run dmesg in the terminal. Need root permission I guess ... But there is no sudo Any hints? Thanks. So it's probably matter of how the kernel is configured. Regards Radek ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No QSerialPort
On 03/26/2014 07:34 AM, Radek Polak wrote: On Tuesday, March 25, 2014 12:32:34 PM wsvries wrote: > Don know about OTG, but my Linux systems always attach a Generic Serial > Driver to the devices. > Why is Sailfish acting differently? No idea how this is in jolla but in openmoko there were options while configuring linux kernel how the device will act when connected to PC . IIRC it was somewhere in USB/gadget menu. You could choose the device to act as USB mass storage, USB ethernet or the USB serial devices. I just tried it connecting and run dmesg in the terminal. Need root permission I guess ... But there is no sudo Any hints? Thanks. So it's probably matter of how the kernel is configured. Regards Radek ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] RPM validator question
Thanks a lot ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] RPM validator question
Hi, On 25.03.2014 20:59, Iosif Hamlatzis wrote: The QtCreator IDE under the Harbour Tools provides an RPM validator. I just wanted to test my package but I get the message the file is too large. Is there a maximum file size only for the validator or also for the actual jolla shop? Yes there is a limit in the web frontend 'Harbour Tools', it's ~40MB. The used web server somehow can't handle bigger files and we didn't had yet time to investigate it. You can do the check also on CLI: On Linux, login to the Build-Engine virtual box: $ ssh -p -i ~/SailfishOS/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost then inside the build engine: $ rpmvalidation.sh harbour-myapp-0.1-4.arch.rpm In that case the limit is the /tmp size (unpacked rpm) which is ~249MB in the build engine. br Reto ___ SailfishOS.org Devel mailing list
