Messages

1

Angstrom & OpenZaurus / Kexec For 2.4.x/arm

« on: April 04, 2011, 09:54:38 am »

Thank you!

I'll give it a try on my collie very soon.

2

6000 - Tosa / Angstrom Status On Tosa

« on: December 24, 2008, 06:29:48 pm »

please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin
It should fix the power key problem.

It does.   But are all of the debug options turned on?  It's very noisy!

Most probably the debug is on as it's unstable release. At least I didn't do anything special for enabling it

Also, I was playing around a bit and got e-wm installed and running up to the point where locale is asked for...but it doesn't seem to register the touch screen.  Is that a kernel thing, or an e thing?

As the ts does work in opie, I'd assume that this is the E problem.

3

6000 - Tosa / Angstrom Status On Tosa

« on: December 23, 2008, 04:35:32 am »

could you please post the result of

Code: [Select]

# grep Name /proc/bus/input/devices
N: Name="Tosa Keyboard"
N: Name="wm97xx touchscreen"

Also please check the exact version of kernel package in those images.

Not sure what you meant specifically, but here's:

Code: [Select]

# uname -a
Linux tosa 2.6.24 #1 PREEMPT Fri Nov 21 16:46:51 MSK 2008 armv5tel unknown

I see... please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin
It should fix the power key problem.

BTW: apm -s worked quite nicely.  Hardware button brought Tosa back to life.  I had to reset my network settings (which brought back wifi), but at least the module wasn't frozen.

As assumed.

4

6000 - Tosa / Angstrom Status On Tosa

« on: December 21, 2008, 05:47:32 am »

Just tried it out.  Show stopper is apparently the keyboard does not work.  "new user details" screen is the first...but neither HW or SW keyboard are placing text in the fields.  Orange lines are back too.  This is with the above installkit and Dmitry's kernel.

For the keyboard, etc. I'm waiting for general Angstrom decision about future of X11 images (will they contain Kdrive or Xorg and which version).

Suspend did not work via hardware on this image either.  What's the command?

I generally use apm -s. However if the "power" button doesn't work, could you please post the result of

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']grep Name /proc/bus/input/devices
grep Handlers /proc/bus/input/devices[/div]

Also please check the exact version of kernel package in those images.

5

6000 - Tosa / Angstrom Status On Tosa

« on: December 09, 2008, 08:40:32 pm »

Speaking of keymappings;  I did an

Code: [Select]

ipkg update, ipkg upgrade

Angstrom 2008 uses opkg. Do you track 2008 (unstable) or 2007 (stable) branch?

which eliminated my ability to get to the Fn generated keys (numbers, punctuation, etc...)

Suspend still has the problem of freezing the prism2_usb module.  Can't reload (unload or load) this module after suspend.

The workaround was pushed into 2008 branch. If you do track 2007.1, get apm-tosa-suspendfix package from 2008 feed
and install it.

I've noticed some other behaviors; but they're specific to Opie or GPE.

Tell me more, please
Most probably there should be several problems related to incorrect keymappings,

I did not test GPE at all for a long time. Currently busy with work, RL, providing upgraded kernel via OE (I plan to provide 2.6.27 or 2.6.28-rc soon) and fixing opie issues.

6

Software / Sharp Camera Software

« on: December 09, 2008, 08:08:13 pm »

Indeed. It was _really_ awful, but then again... some folks can do art with fewer pixels

It's quality is awful. However it's bearable at QVGA. The design of camera is flawed from several points of view. The thing I'm trying to fight currently is interference with luminiscent lamps.

7

Qt/Qtopia / Qtopia 2.2 Compilation And Pngscale Error (solved!)

« on: December 09, 2008, 02:54:46 am »

Qtopia 4 is good, but wat with performance? I had heard, that the qtopi4 is very slow on zaurus machines.

qt-embedded-3 was apparently a real hog, but qt-embedded- (oops, qt-core-)4 is said to be better as it's more modular? I would guess that, inevitably, because it's more advanced it will need more resources, but whether that makes it unusable also depends on how well the applications can make use of shared libraries etc to maximise efficient use of code space.

I've tried qt-extended 4.4.2 on my tosa. It looked pretty much impressive from the point of "beauty/sexy/etc.". However it was really resource hungry. Maybe it's just the lack of graphic acceleration, maybe not, but it feeled a bit "sloow". Just a bit, but not that bit one could probably live with.

8

6000 - Tosa / Considering Graphic Driver For Tosa

« on: December 07, 2008, 09:21:16 am »

Most Tosa hardware on Angstrom works?

If smth. doesn't work, please fill bugs in OE, assigning them to me.

9

6000 - Tosa / Help Files & Bluetooth

« on: December 06, 2008, 06:56:01 am »

The english firmware for SL-6000W was once posted here. Please google for "SL-6000W-ENG-NAND-original.zip".
Ask again if you need instructions about reflashing it.

10

6000 - Tosa / Angstrom Status On Tosa

« on: December 04, 2008, 11:00:39 am »

--edit-- hm, doesn't seem to suspend. is that normal?

It suspended for me using the menu (QPE, or Opie); not with the button.  Comes out of suspend via the button, however.

I'll have to look upon this.

Today the fix went in in the .dev branch. It was just two missed lines in defconfig-tosa. I'll still have to check the keys mappings, check GPE problems etc.

11

6000 - Tosa / Angstrom Status On Tosa

« on: December 03, 2008, 08:42:51 pm »

I'm not sure you can ever change the update menu, there's an immutable block of flash for recovery, this is why zaurus is hard to brick.

There is a "diagnostic" menu in ROM, which can not be removed. OTOH "update" menu lies just in bare NAND and can easily be removed (e.g. by installing u-boot).

12

6000 - Tosa / Considering Graphic Driver For Tosa

« on: December 03, 2008, 07:45:15 pm »

Most 6000 users are probably using frame buffer driver with the qt2 based default Sharp ROM.

Sharp's qt2 does have a driver for tc6393, it accelerates blt and fill functions.

This is due to not really having much to choose from. Most other 6000 ROMs are incomplete. Mplayer and/or Quasar compatible driver would be nice to make videos smoother.

I'm using angstrom 2008 + opie now and I'm looking towards Qtopia4 and/or OpieII.
OTOH When I was using it with GPE-based environment, it was also usable.

13

6000 - Tosa / Angstrom Status On Tosa

« on: December 03, 2008, 08:37:55 am »

Unfortuantely the only NAND backups I have been able to find are Japanese and while that looks cool and all my Japanese is not really up to par.

There are several topics about NAND backups on this forum. Also the page about tosa on www.oesf.org should contain a link to SL-6000 NAND backup. Please take care to check.

14

6000 - Tosa / Considering Graphic Driver For Tosa

« on: December 02, 2008, 11:43:24 am »

I'm considering writing accelerated graphic driver for tosa. At least it will bring support for blits/stretchblits from vram, which can accelerate things a bit. The question is which graphic engine to start with? Which engine is the most demanded/used by the community?

15

6000 - Tosa / Angstrom Status On Tosa

« on: December 02, 2008, 08:23:09 am »

--edit-- hm, doesn't seem to suspend. is that normal?

It suspended for me using the menu (QPE, or Opie); not with the button.  Comes out of suspend via the button, however.

I'll have to look upon this.

Still no access to increasing / decreasing backlight via settings on either opie or gpe, haven't tested sound through alsa(mixer, player, etc...), but wifi is working (open network at least)!

I've committed the fix for the opie to .dev branch to support backlight setting. I'll have to look into GPE, but that may need time, as I'm more dedicated to opie for now. The patch should be
pretty easy though (check opie commit).