Re: extras-assistant: autobuilder fails, no reason given?
Hi Tom, some build errors will not be displayed in the log. I had the same problem and i checked the build process manually: [2010-11-06 22:34:16] Extracting sources to work dir [2010-11-06 22:34:16] cd /home/builder2/maemo-fremantle-i386-extras-devel/work && dpkg-source -x recaller_2.1.0-1.dsc [2010-11-06 22:34:17] dpkg-source: warning: extracting unsigned source package (recaller_2.1.0-1.dsc) dpkg-source: info: extracting recaller in recaller-2.1.0 dpkg-source: info: unpacking recaller_2.1.0-1.tar.gz [2010-11-06 22:34:17] cd /home/builder2/maemo-fremantle-i386-extras-devel/work/recaller-2.1.0 && dpkg-checkbuilddeps [2010-11-06 22:34:17] Cleaning up... [2010-11-06 22:34:17] Removing temporary target... [2010-11-06 22:34:17] Done. Check all commands (see the log) manually in the terminal (cd, dpkg-source, dpkg-checkbuilddeps). My error was for example in the descriptions field of the application. I mean it was a mistake with a space or a newline. with kind regards Patrick Am Samstag, den 06.11.2010, 22:02 +0100 schrieb Thomas Waelti: > Hello all > > Autobuilder fails on my uploads, but I can't find the reason in the logs > available. > Any ideas on how to proceed? Did I overlook something? > > You can find more info about this build here: > https://garage.maemo.org/builder/fremantle/recaller_2.1.0-1/ > > Thanks > -Tom > > > > > > [2010-11-06 22:34:01] Processing package recaller 2.1.0-1. Uploader: > > twaelti, builder: builder2 > > [2010-11-06 22:34:03] Building recaller 2.1.0-1 for target > > 'maemo-fremantle-i386-extras-devel' > > [2010-11-06 22:34:17] FAILED > > [2010-11-06 22:34:17] You can find more info about this build here: > > https://garage.maemo.org/builder/fremantle/recaller_2.1.0-1/ > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
extras-assistant: autobuilder fails, no reason given?
Hello all Autobuilder fails on my uploads, but I can't find the reason in the logs available. Any ideas on how to proceed? Did I overlook something? You can find more info about this build here: https://garage.maemo.org/builder/fremantle/recaller_2.1.0-1/ Thanks -Tom > > [2010-11-06 22:34:01] Processing package recaller 2.1.0-1. Uploader: twaelti, > builder: builder2 > [2010-11-06 22:34:03] Building recaller 2.1.0-1 for target > 'maemo-fremantle-i386-extras-devel' > [2010-11-06 22:34:17] FAILED > [2010-11-06 22:34:17] You can find more info about this build here: > https://garage.maemo.org/builder/fremantle/recaller_2.1.0-1/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Problem installing ESBox
I'm trying to install ESBox for Eclipse but can't get a response from http://maemoide.nokia.com/updates/2.0/esbox Is the link out of date or is the server down? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: USB host mode on N900 (was Re: N900 usb host + power charge)
[Paul Fertser Di 8. Dezember 2009]: > Hi, > > On Mon, 21 Sep 2009 00:01:41 +0300, Igor Stoppa wrote: > > On Sun, 2009-09-20 at 22:56 +0200, ext Kees Jongenburger wrote: > > > On Sun, Sep 20, 2009 at 9:02 PM, Igor Stoppa wrote: > > > > Add to that several HW bugs that were discovered during the > > > > development > > > > and needed workarounds. > > > > > > Does this simply mean it's not possible at all? not even for example > > > booting in HOST only mode? > > > > AFAIK no. Not even that. Note that i'm no USB expert, but if i have > > understood correctly, part of the configuration is done > > automatically by the transceiver and that cannot be done because of > > the missing line from the connector that would identify the port as > > A type. > > I'm no USB expert either but given what i already know about it, i > think more hardware information is needed to be able to give a final > verdict on the N900 usb host mode functionality. I'm not talking here > about perfectly correct standards implementation or certification > issues though i personally would prefer to have a working hostmode > implementation to having a useless usb logo on the box. > > So, a bit of theory first: > > 1. n810 analogy doesn't work here since n810 uses a dedicated usb > controller (tusb6010b) along with a power management ic (tps65030) > while n900 uses an integrated Mentor Graphics OTG controller (musb > mhdrc) and other components still unknown to the general public. > > 2. For "true" OTG operation a dedicated line should be routed from the > "ID" pin of receptable to the MUSB core. > > 3. For a device to act as a slave a "strong" 1.5k pullup should be > connected to the DP line, this way a slave signals its presence. > > 4. For a device to act as a host two 15k pulldowns should be connected > to DM and DP lines. If actual hardware lacks those, they can be easily > connected externally, along with the peripheral equipment. > > 5. MUSB has output pins to control the necessary resistors and > external circuits to provide power on Vbus. > > 6. Even in traditional usb-host <-> usb-device scenario power on the > 5V line can come from either side, one can e.g. modify a powered hub > in a way to provide power both to the host and to the peripherals, and > since host charging circuit is generally independent from the usb > controller, one most likely can use a hub like that to charge host and > to enable usage of slave devices at the same time. Probably current > musb driver doesn't support this scenario yet but it shouldn't be hard > to implement. > > 7. I can't tell for sure because MUSB "datasheet" looks like a parody > but it seems highly unlikely that it's impossible to manually switch > musb to the host mode. > > Now, the questions: > > 0. Is there any real show-stopper to use USB host mode? > > 1. Does n900 have an integrated curcuit to provide power to the > external devices over usb and if yes, what is it and how is it > connected/controlled? > > 2. Does n900 have the necessary 15k pulldowns in place? > > 3. Is it indeed the connection between the ID pin on usb receptable > and musb that is missing? It'd look strange to not route that line, > even if the hostmode/otg is not fully functional, it's only one > possibly useful line after all. > > 4. What HW bugs you mentioned are still present in the mass-produced > devices, how do they affect usb operation? > > 5. Since musb driver doesn't seem to be in a particularly good shape, > is it possible that some problems nokia engineers faced are software > issues and hence can be fixed? What were they? > > Looking forward to your reply, TIA :) > Happy hacking! It's a pity nobody ever answered those questions, as it would have saved us an Olympus Mons of troubles we had to go through, to find out about all that by ourselves, with ZERO support from Nokia. Whatever, Nokia said it's not possible, I always said it's impossible that this is not possible, so finally hostmode taskforce team [1] proudly presents: * USB HOSTMODE ON N900 * * * see https://garage.maemo.org/pipermail/h-e-n-devel/2010/35.html https://garage.maemo.org/plugins/ggit/browse.php/?p=h-e-n;a=commit;h=d7f76e505b16f7e9305c59c51d02fb1473ab5b2c [1] hostmode taskforce team mostly are the gals and guys listed as members of h-e-n.garage.maemo.org Joerg Reisenweber System Architect, Senior EE, Consultant signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: calendar-backend API: CCalendar's entries empty
Hi Nicolai,
thanks for the valuable hint. The problem, as it turned out, was a
classical PEBCAK (*). In Qt Developer, I used user "developer" to deploy
on my N900. Therefore, this user's calendar was queried, returning zero
entries ;)
So switching to "user" solved the problem.
However, thanks for your answer!
Best,
Filip
---
(*) Problem Exists Between Chair And Keyboard ;)
On Fri, 2010-11-05 at 17:22 +0100, Nicolai Hess wrote:
>
>
> 2010/11/5 Filip-M. Brinkmann
> Hi all,
>
> I'd like to code a small Todo-list widget, which shows all due
> to-dos on
> the desktop.
> I started today, but I cannot access the to-dos because the
> CCalendar
> instances don't return any entries.
> I have 2 Calendars on my N900 and I get two calendar instances
> back,
> which is fine. They return the correct names and attributes,
> but are
> otherwise unresponsive. ;)
> so, for instance the following code returns 0 as to-do count:
>
> ...
>
> QString output;
> int count=0;
> int error;
>
> CMulticalendar* mcal = CMulticalendar::MCInstance();
> vector cals = mcal->getListCalFromMc();
> for(std::vector::iterator it = cals.begin(); it !=
> cals.end(); ++it){
> // here, I get those 2 calendars correctly
>
> // next line sums up to 0 all the time
> count +=
> (dynamic_cast(*it))->getTodos(error).size();
>
> // next line shows the calendar names
> cerr << (dynamic_cast(*it))->getCalendarName();
> }
>
> output= QString("Found %1 todos.").arg(count);
> // count is 0 here, although I have like 20 todos in one
> calendar
> return output;
>
> --
> Same behaviour shows on getEvents() and so on...
>
> Since documentation is...ehm... not very complete:
> does anyone know what happens there?
>
> cheers,
>
> filip
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>
>
> For debugging purpose you can create an empty file:
> /home/user/.calendar/log
> (reboot may necessary)
>
> This file indicates the calendar-backend to log ALL sql and results
> as syslog messages.
> Now you can see which sql and parameters are called for example to
> retrive all todos with
> "getTodos()"
>
> Btw pay attention, that methods like this one:
> (dynamic_cast(*it))->getTodos(error).size();
>
> create a vector with dynamically allocated objects, and you have
> to free them.
>
> regards
> nicolai
>
>
>
>
>
>
>
signature.asc
Description: This is a digitally signed message part
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
