Franky Van Liedekerke wrote:
> Hmm ... I'm pretty sure I saw my phone suspending while connected ... I
> will test this more.
>
> F.
Filip's patch fixes this for me. I have tested it quite thoroughly. But
it's not included in my image yet.
Radek
___
; F.
>
> On Thu, 02 Apr 2009 09:22:33 +0200, Franky Van Liedekerke
> wrote:
>
> > On Wed, Apr 1, 2009 at 8:48 AM, Filip Onkelinx wrote:
> >
> >> Hi,
> >>
> >> attached is a patch to use uevent to get kernel notifications for
> >>
tch to use uevent to get kernel notifications for
>> 'usb-cable-changed' in QtExtended on recent kernels (>=2.6.28).
>> On 'older' kernels (<2.6.28), this information was comming in trough
>> /dev/input/event4 but this is no longer working (there is a t
On Wed, Apr 1, 2009 at 8:48 AM, Filip Onkelinx wrote:
> Hi,
>
> attached is a patch to use uevent to get kernel notifications for
> 'usb-cable-changed' in QtExtended on recent kernels (>=2.6.28).
> On 'older' kernels (<2.6.28), this information was commi
That's great..Now QtEI should work better on kernel 2.6.28. I will do a
test soon.
On Wed, Apr 1, 2009 at 2:48 PM, Filip Onkelinx wrote:
> Hi,
>
> attached is a patch to use uevent to get kernel notifications for
> 'usb-cable-changed' in QtExtended on recent kern
Hi,
attached is a patch to use uevent to get kernel notifications for
'usb-cable-changed' in QtExtended on recent kernels (>=2.6.28).
On 'older' kernels (<2.6.28), this information was comming in trough
/dev/input/event4 but this is no longer working (there is a
On Wed, Jan 28, 2009 at 10:52 AM, Matthias Apitz wrote:
>
> Hello,
>
> Maybe a stupid question: the FR's USB cable has something special wired
> or can I use any other USB cable which fits, for example the one of my
> Canon cam? Thx
>
You can use any that fits. To
Hello,
Maybe a stupid question: the FR's USB cable has something special wired
or can I use any other USB cable which fits, for example the one of my
Canon cam? Thx
matthias
--
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
. The only way I got any
life out of it was by attaching the usb cable and trying again.
And that's the way it still is.
If I want to boot up my phone, I have to attach it to the usb cable or
it won't do ANYTHING.
I have already flashed u-boot, I have installed the 4.3.2 version of
qt
On Thursday 04 September 2008 04:56:48 sledgeas wrote:
> Yhaw!
> It was enough today just to flash this:
> http://downloads.openmoko.org/releases/Om2008.8-update/Om2008.8-gta02-20080
>903.uImage.bin and cdc_ether immediately gave out usb0 (before to even get
> the usb `new full speed USB device
Yhaw!
It was enough today just to flash this:
http://downloads.openmoko.org/releases/Om2008.8-update/Om2008.8-gta02-20080903.uImage.bin
and cdc_ether immediately gave out usb0 (before to even get the usb `new
full speed USB device using uhci_h' line, I had to suspend and then
wake up.
S
Sarton O'Brien wrote:
> On Wednesday 03 September 2008 10:32:17 sledgeas wrote:
>
>> Please, refer to this
>> http://n2.nabble.com/Can-bad-NAND-blocks-cause-USB%27s-%22device-descriptor
>> -read-64%2C-error--110%22---tp835094p835094.html for more full info.
>> A guy in #openmoko suggested my fla
On Wednesday 03 September 2008 10:32:17 sledgeas wrote:
> Please, refer to this
> http://n2.nabble.com/Can-bad-NAND-blocks-cause-USB%27s-%22device-descriptor
>-read-64%2C-error--110%22---tp835094p835094.html for more full info.
> A guy in #openmoko suggested my flash blocks might be bad and fs not
Please, refer to this
http://n2.nabble.com/Can-bad-NAND-blocks-cause-USB%27s-%22device-descriptor-read-64%2C-error--110%22---tp835094p835094.html
for more full info.
A guy in #openmoko suggested my flash blocks might be bad and fs not
really dealing with them ok. - could this be causign the usb
>
> If using those images doesn't work then it's sounding like some kinda hardware
> fault.
>
> Good luck!
>
8(
--
sledge
Sarton O'Brien rašė:
> On Wednesday 03 September 2008 02:49:58 sledgeas wrote:
>
>> I am having the same problem as Kevin once had, now. I have immed
>> reflashed my
Thanks for the answer, but referring to my next email (yes, I have tried
to use the correct kernel):
> from openmoko2008 update site:
> Om2008.8-gta02-20080826.uImage.bin - this one says bad kernel image
The exact error of NOR and NAND (when using 20080826 kernel and 20080831
or 20080901-2 rootf
On Wednesday 03 September 2008 02:49:58 sledgeas wrote:
> I am having the same problem as Kevin once had, now. I have immed
> reflashed my FR's om2007 with 2008 and kernel:
> tried these:
> from openmoko2008 update site:
> Om2008.8-gta02-20080826.uImage.bin - this one says bad kernel image
> these
On Wednesday 03 September 2008 01:35:50 sledgeas wrote:
> Hello,
>
> I am getting same error. I got my FR last week. I reflashed om2007 with
> 2008.8 using:
>
> Om2008.8-gta02-20080831.rootfs.jffs2
> gta02v5_and_up-u-boot.bin
> testing-om-gta02-20080831.uImage.bin
You're using a testing kernel. Yo
there, error -110):
Om2008.8-gta02-20080831.rootfs.jffs2
testing-om-gta02-20080831.uImage.bin
testing-om-gta02-20080902.uImage.bin
gta02v5_and_up-u-boot.bin (Aug 26th)
Tried various ways (booting with/without usb cable, plugging it later
etc.), re-inserting uhci_hcd etc.
cdc_ether and usbnet com
few days not using the usb cable and an opkg update and an
> system update (Ubuntu with Kernel 2.6.24-20), the cable doesn't work
> anymore.
>
> Dmesg says:
>
> [ 211.983257] usb 1-1: new full speed USB device using uhci_hcd and
> address 2
> [ 227.081309] usb 1-1:
; possibly forgetting to switch it back before plugging it into a
> computer, and possibly destroying the USB port on the computer and/or
> the FR. A dedicated charging cable would make this simpler.
>
> Problem is, the ID pin apparently exists only on the Mini-B connector,
> and doesn'
On 2008-08-27, Al Johnson <[EMAIL PROTECTED]> wrote:
> On Wednesday 27 August 2008, Daniel Dadap wrote:
> > Problem is, the ID pin apparently exists only on the Mini-B connector,
> > and doesn't have a corresponding wire inside the USB cable. Has
> > anybody on the
gmane.org not forwarding emails correctly? sorry for double posting in
case it gets fixed. see my post bellow:
On Wed, 27 Aug 2008 17:45:36 +0200
Harald Koenig
<[EMAIL PROTECTED]>
(HK) wrote:
>I've modified battery.py a bit to display the (de)charging current too,
>my script version attached...
On Wed, 27 Aug 2008 17:45:36 +0200
Harald Koenig
<[EMAIL PROTECTED]>
(HK) wrote:
>I've modified battery.py a bit to display the (de)charging current too,
>my script version attached...
Cool :) I had to erase the first ^M after python and then all is great,
thank you :)
Btw, is there a way to see
On Aug 27, Daniel Dadap wrote:
> Hello Community,
>
> I just bought a portable USB battery pack ( one of these:
> http://apc.com/products/family/index.cfm?id=314 ) to use with my
> FreeRunner so that I could keep tangogps running to log a track for me
> during a bike ride. It worked quite well: I
On Wednesday 27 August 2008, Daniel Dadap wrote:
> Problem is, the ID pin apparently exists only on the Mini-B connector,
> and doesn't have a corresponding wire inside the USB cable. Has
> anybody on the list done USB connector hacking, and have any tips on
> how to get a
Start searching the archives - the cable hacking was covered weeks ago,
and there is also a software control that can be used.
Billk
On Wed, 2008-08-27 at 09:00 -0400, Daniel Dadap wrote:
> Hello Community,
>
> I just bought a portable USB battery pack ( one of these:
> http://apc.com/products/f
Daniel
> Problem is, the ID pin apparently exists only on the Mini-B connector,
> and doesn't have a corresponding wire inside the USB cable. Has
> anybody on the list done USB connector hacking, and have any tips on
> how to get a resistor in there without interfering with pl
r and/or
the FR. A dedicated charging cable would make this simpler.
Problem is, the ID pin apparently exists only on the Mini-B connector,
and doesn't have a corresponding wire inside the USB cable. Has
anybody on the list done USB connector hacking, and have any tips on
how to get a resisto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| hm ok,
|
| With today's opkg update && opkg upgrade the usb networking is now
| working again :).
Great.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fe
hm ok,
With today's opkg update && opkg upgrade the usb networking is now
working again :).
Am Dienstag, den 05.08.2008, 11:47 +0200 schrieb Kevin Zuber:
> Hi Andy,
>
> thanks for your quick answer!
>
> Ok, that's the reason for the problem but it doesn't fix it completely.
> After flashing ubo
Hi Andy,
thanks for your quick answer!
Ok, that's the reason for the problem but it doesn't fix it completely.
After flashing uboot (flashing works quite well so no problem with the
cable) there was no more error message but also no success message.
If I connect now my Freerunner to the usb port
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| So it should be the cable (hardware defect?) oder the neo update (using
| 2007.2 with latest updates).
| Did I miss something, any other ideas? Has someone this problems, too?
|
| It also seems, that the ne
Hi Community,
After a few days not using the usb cable and an opkg update and an
system update (Ubuntu with Kernel 2.6.24-20), the cable doesn't work
anymore.
Dmesg says:
[ 211.983257] usb 1-1: new full speed USB device using uhci_hcd and
address 2
[ 227.081309] usb 1-1: device descr
34 matches
Mail list logo
