Re: How much are Nxxx open?
On Tue, 1 Sep 2009, Frantisek Dufka wrote: Nicola Mfb wrote: With N900 we don't know yet but hopefully the bootloader will be u-boot. That's nice, the best would be if we'll be able to update/replace u-boot, and have a way to debrick the device if something goes wrong. u-boot is just my guess, any other choice does not look sane to me, but still it can be a wrong guess. OMAP3 is designed to be unbrickable, it can boot from usb or serial or mmc directly from its boot ROM, bootloader in flash is not needed. I'm not sure how configurable is the priority list for booting (i.e. if it could be locked to load bootloader only from NAND flash) but hopefully it will by possible to bypass even the bootloader in NAND(u-boot or whatever). Boot configuration priorities are controlled through specific pins on the device, which might be hardwired on the device board to force a specific configuration. Disabling USB boot entirely from the booting sequence is possible. There might be security concerns with USB booting, but large customers, such as Nokia, may be also able to push features to the internal boot ROM that solve these issues. See OMAP34xx Wireless Technical Reference Manual (SWPU114U_FinalEPDF_08_17_2009.pdf), 26.2.3 Boot configuration for more detailed explanation. -kirma ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: What does Nokia's acquisition of Trolltech mean to Maemo?
On Mon, 28 Jan 2008, =?UTF-8?Q?Beno=C3=AEt=20HERVIER=20 wrote: I think their are more interested by the OS Qtopia Phone Edition than QT on Maemo. Although this has some backing on the press release, it's still my personal speculation: Qt is reasonably portable, and Nokia has already demonstrated that Open C works on the S60 platform. I don't think they're directly interested of any specific platform; rather, they would distance themselves from strong reliance on Symbian platform. That could make the applications reasonably portable to future (even unknown!) platforms on the source code level by building up a relatively OS-agnostic development environment; in this case Open C, Qt and some other less Symbian-specific APIs would make it reasonably easy to build applications for both S60 and future platform, be it Linux if you want to say so. As the growth of device capabilities has made Open C (and probably Qt) practical on the phones, supporting Qt along with the current environment on future tablets could as well be not a such a far-fetched idea to think of. -kirma ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] What is the 770 display hardware able to accalerate?
Gustavo Sverzut Barbieri [EMAIL PROTECTED] wrote: On 11/7/05, Clemens Eisserer linuxhippy at gmail.com wrote: Hi there, I just read that the 770 display hardware is quite slow but on the other hand it supports pixel doubling which isn't such a trivial feature at all. I think you mis understood that mail. 1) pixel doubling is trivial, instead of painting one pixel at (x,y), you paint 4 pixels at (2x,2y), (2x, 2y+1), ( 2x+1, 2y) and (2x+1, 2y+1 ). 2) dealing with large pictures, so much data, consumes lots of CPU cycles, that nokia 770 doesn't have (200mhz arm) Does anybody know which operations are (at least partially) accalerated by the integrated graphic controler - e.g. are fills/draw/blit operations which are done by xlib accalerated? Does the target surface play a role wether it can be accalerated (e.g. can fills/blits to or from a pixmap be accalerated)? I don't know, let someone that knows the hardware better reply this part. Before I got my 770 today, I browsed through OMAP1710 documentation and related kernel sources. OMAP1710 claims to perform 2D graphics acceleration according to marketing page, but in practice, this boils down to a very programmable DMA engine - it can perform, among other things, image rotation (for RGB, at least), blitting, color-masked blitting, and constant filling. OMAP1710 also has a reasonably powerful, and potentially very underused TI DSP counterpart which has specific accelerators, of which DCT decoding is probably of most interest (for video playback). I don't know how fast it could perform color space conversions. I've heard that Nokia 770 doesn't use the built-in LCD controller in OMAP1710, but uses a specific chip for this purpose - supposedly to improve performance. Kernel source file drivers/video/omap/hwa742.c contains rather scantily documented code for this Epson chip, which obviously can perform color space conversion from YUV422 and YUV420 formats to native RGB. It also does the pixel doubling, and I have a hunch it can do other things, such as framebuffer rotation, but it's next to impossible to understand how that functionality could be programmed, since publicly available documentation is lacking. I would be very glad to hear especially about HWA742, and especially regarding possibility to implement framebuffer rotation (also for non-RGB color spaces) on hardware to implement it efficiently on X11 (for instance, 180 degree rotation for left-handed users would be great). Sadly enough, even though there are things that can improve certain scenarios, memory speed is probably the largest bottleneck. -kirma ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
