Active Topics

 


Reply
Thread Tools
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#201
Originally Posted by thp View Post
No arguments against it so far - how do we proceed?
I say we go for it. I just emailed Tuomas (and CC'd you, hope that's OK).
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#202
Originally Posted by scaler View Post
Sorry I can't tell you how stable etc. - I'm not that far advanced.
Right. I don't have much time to experiment with this at the moment, but could you add it to the wiki so it doesn't get forgotten? Any links to previous discussions, experiments etc with OHCI would be most welcome.
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#203
Originally Posted by martinsmc View Post
Is possible add bug 3415 ??
If you mean the workaround from http://wnd.katei.fi/maemo/workaround-3415/ my opinion is no. Reasoning:
  • the bug affects only a small proportion of devices
  • the workaround reduces battery life
  • there's nothing in the community SSU that conflicts with it so N810 owners who want/need it can still have it.
 

The Following 2 Users Say Thank You to lma For This Useful Post:
Posts: 99 | Thanked: 65 times | Joined on Jan 2008 @ Finland
#204
Originally Posted by lma View Post
If you mean the workaround from http://wnd.katei.fi/maemo/workaround-3415/ my opinion is no. Reasoning:
  • the bug affects only a small proportion of devices
  • the workaround reduces battery life
I fully agree with "no". This workaround helps me to deal with the issue but it's not a fix. In fact, it could be just good old snake oil packed in a pretty Debian package.
 

The Following User Says Thank You to wnd For This Useful Post:
Posts: 8 | Thanked: 2 times | Joined on Feb 2010 @ Brasil / Curitiba
#205
Originally Posted by lma View Post
If you mean the workaround from http://wnd.katei.fi/maemo/workaround-3415/ my opinion is no. Reasoning:
  • the bug affects only a small proportion of devices
  • the workaround reduces battery life
  • there's nothing in the community SSU that conflicts with it so N810 owners who want/need it can still have it.
Ok,really workaround is not a good solution, tks. I think if any correction to this is Frementale...

My device reboot every day, 2 or 3 times... it is a not good.

Tks
 
Posts: 42 | Thanked: 8 times | Joined on Jun 2007 @ Mexico
#206
I installed the community SSU on my N800 yesterday and been testing apps and everything seem to work fine.
 

The Following User Says Thank You to rafaelsemx For This Useful Post:
Posts: 154 | Thanked: 73 times | Joined on Jan 2009 @ Toronto
#207
Originally Posted by lma View Post
.. could you add it to the wiki so it doesn't get forgotten?
Thank you very much for your willingness to include this in the project. I am not sure that it counts as "low-hanging fruit".

Because of the broken link, I am unable to add the following material to the wiki entry, and I apologize for creating this long post instead. EDIT: Thanks for your guidance on Wiki use in response to this.

In reading Bug 3281 , it is evident that the problem extends beyond cameras to the other devices discussed in http://people.freedesktop.org/~dkuka...e-capabilities.

There are standard procedures, described e.g. in http://people.freedesktop.org/~dkuka...perties-camera, for overcoming the kernel conflicts that arise in desktop distros which have automounting of USB storage devices. These procedures do not work in the MUSB configuration of OS2008, where the drivers for probing endpoint devices are bundled together with automounting drivers in the g_file_storage module.

(The conflicts do not exist in distros without automounting of USB storage.)

gphoto2 runs without problems on the Nokia 770, where USB host mode operates as it does on a desktop computer, through a dedicated host port controlled by OHCI. (It differs from a desktop computer in needing external power for the transceiver, but that is not relevant to the present case.) There is no automounting of USB storage, and therefore no need to configure HAL to recognize the camera as something other than storage.

I suggest that the best hope of resolving Bug 3281 lies in similarly providing an optional OHCI controller that could temporarily replace the MUSB + g_file_storage control in OS2008.

Last edited by scaler; 2010-03-28 at 12:15. Reason: Removed references to Bug 2491, which deals with a different problem
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#208
Originally Posted by scaler View Post
I am not sure that it counts as "low-hanging fruit"
Yeah, it will probably have to wait a while until someone has time to test it.

although I see that someone else has already made wiki entry 2491 (link broken), which describes my reason for making this request.
That's bug 2491, which seems unrelated to USB.

(The cause of the broken links is bug 9736, just replace apps with bugs in the hostname until it's fixed).

I am unable to add the following material to the wiki entry, and I apologize for creating this long post instead.
Feel free to add it to http://wiki.maemo.org/Talk:Diablo_Community_Project

Last edited by lma; 2010-03-27 at 11:27. Reason: #!$@%!@$% automatically-added smilies
 

The Following 2 Users Say Thank You to lma For This Useful Post:
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#209
Just pushed another update that includes a patched kernel & xserver. Both my tablets survived it, but you have been warned.
 

The Following 2 Users Say Thank You to lma For This Useful Post:
Posts: 206 | Thanked: 46 times | Joined on Mar 2010
#210
updated successfully. no problems. Awesome stuff. what did the patches do?
 

The Following User Says Thank You to cstryon For This Useful Post:
Reply

Tags
backintime, diablo cssu, diablo turbo


 
Forum Jump


All times are GMT. The time now is 20:51.