Messages

1

6000 - Tosa / Current Status Of Tosa In Feb 2010

« on: March 14, 2010, 04:53:02 pm »

Alright, I just got a serial cable, so hopefully I can see what's going on with it.

I'll try some of the newer kernels and see if I can't figure out what's up with them.

2.6.33 is showing some odd problems. It boots once each time, and it's somewhere running out of memory, udev quickly gets killed by the oom killer. If anyone wants to investigate, I've got a log off the serial port. I'm currently trying via disabling things until something works. It's tending to just stop (screen and serial) most of the time, unfortunately.

2.6.29 has the problem of (as I've probably stated) calling dma_free_coherent with interrupts disabled. I may have found a possible problem with the particular code problems, relating to a few checks which apparently caught it, possibly indicating it should be using a different path, I'll test this and find out.

2

6000 - Tosa / Current Status Of Tosa In Feb 2010

« on: March 13, 2010, 06:32:03 am »

Alright, I just got a serial cable, so hopefully I can see what's going on with it.

I'll try some of the newer kernels and see if I can't figure out what's up with them.

3

6000 - Tosa / Current Status Of Tosa In Feb 2010

« on: March 07, 2010, 07:59:11 am »

I've started poking around your git repository, unfortuantely, your instructions on building it aren't that helpful, specifically this: "build and install SlackBuilds/crossed-linux" is that a slackware specific thing, or is there some way of doing that outside of slackware?

(It's been AGES since I looked at slack, and I think the last time I used it was zipslack transfered with floppies...)

SlackBuilds are shell scripts that build Slackware packages. (in very short a slackware package in just a tar.gz archive with 2 optional files, install/{doinst.sh,slack-desc}. Building a package consist in compiling, installing in a temporary directory ($PKG in the scripts) and then call slackware's makepkg from this directory to assemble the package itself.)

SlackBuilds/crossed-linux/ is a slackbuild that I made to package a cross-compiled kernel so I don't have to fiddle making symlinks in /boot each time I compile a new kernel. Now since you're not running slackware on your computer this is of little use to you obviously... You could use to config-2.6.31.12 to cross-compile your own kernel and copy the files manually.

the the minirootfs can be found here : ftp://ftp.armedslack.org/armedslack/armed...ols/minirootfs/

Hope this helps, I'll clarify the steps in the git.

I'll mess with that (and what I snipped) and see about getting it working.

Meanwhile I've tried many ways to setup the keyboard in X without success so far... This xkb thing makes HAL look friendly and simple in comparison, what kind of sick mind could possibly come out with such an unholy nightmare is beyond me  

Code: [Select]

$ xmodmap tosa.xmodmap still has no effect and I can't see why.

I've had some problems with that on zubuntu, which I think is using something very close to what you are. I did get some of it working via Corgi's xmodmap, however, note that many of the keycodes aren't the same (1st and 3rd rows are shifted, row 2 is random), but at least it I could tell xmodmap was doing *something*. None of the tosa keymaps I tried (which I think I lost) worked. The command I made it invokes specifically is: "xmodmap /etc/X11/kb/Shepard/xmodmap"

Additionally, I had to replace /etc/keymap-2.6.map (grabbed from an Angstrom image) before the console would work properly. (and even then sometimes the numbers wouldn't, which I think is a problem of the keymap.

4

6000 - Tosa / Current Status Of Tosa In Feb 2010

« on: March 05, 2010, 11:35:46 am »

I've started poking around your git repository, unfortuantely, your instructions on building it aren't that helpful, specifically this: "build and install SlackBuilds/crossed-linux" is that a slackware specific thing, or is there some way of doing that outside of slackware?

(It's been AGES since I looked at slack, and I think the last time I used it was zipslack transfered with floppies...)

5

6000 - Tosa / Current Status Of Tosa In Feb 2010

« on: March 05, 2010, 05:35:34 am »

Happy to announce that touchscreen is working fine in X now

Not bad, I just pulled my /etc/pointercal from zubuntu, if you'd like to compare, unless you did something else?


Somewhere between 2.6.30 and 2.6.33 the tosa screen got broken in terms of being useful. I've only tested 2.6.29 and 2.6.30 so far (I got distracted from fixing that problem.) I don't think it's just the backlight either, for me, I can usually see the screen via reflection, but when trying .33 it was totally blank as far as I could tell. Unfortunately, I don't have a serial port to try and see what's going on there.

As far as sound, I recall it working on my 2.6.29 (which per a request on the angstrom user mailing list, I'll put up when I get time, should be Sat at the latest). So it should work for any 2.6.29. Though http://www.omegamoon.com/blog/index.php?en...ry090716-153753 suggests it's broken in his version of 2.6.31.

I note that you mention "ohci doesn’t like to suspend", do you have usb host working? As for me, while it sorta works (lsusb responds) anything actually trying to use that, like a thumbdrive or the built in wireless, drags it to a halt. Investigating it seems like ohci-hcd got changed between .29 and .33, and at a guess, may work.

Major Outstanding issues I see (please mention any forgot):

• LCD broke in .31 - .33
• USB broken in .29 and .30 (possibly fixed by .33, but I can't tell)
• Sub USB: prism2_usb may be broken, as well as usb being broken. I can't verify this either way though.
• Sound may have broken in .30 or .31

6

6000 - Tosa / Current Status Of Tosa In Feb 2010

« on: February 24, 2010, 11:59:20 pm »

Allow me to introduce myself, and have been involved with the Zaurus since the SL-5500 came out. (I'm probably the first person to get mplayer working.) I used to run OZ and such, but got interested and involved in other projects, given the lack of support of collie (especially the sd, which finally got working) I recently saw an SL-6000L on ebay, and got it. Alas, the current state of support, wasn't as I thought it was from my looking at various sites.

Currently the status of Zaurus for me, broken down by category:
General:
2.6.29 works, except for usb.
As far as I can tell, there is a conflict due to the way the tc6393 chip is accessed. The chip is only accessed via dma, but ohci-tmio and associated ohci calling it with due to patches, which use dma_*_coherent calls, which can't be called with interrupts disabled. Resulting in basically killing any ability to use it after that. If this were fixed, I would consider it fully usable after the distro specific issues (mostly keymaps) are resolved.

I'm working on tracking down what the problem is, but I honestly have not too high of an expectation of success, given my lack of experience with that portion of

2.6.33-rc8 has a compilation error which I have resolved. However, there are issues with the backlight. See: http://www.mail-archive.com/zaurus-devel@l...g/msg00189.html for more information.

Now, with that angstrom (dev branch):
Opie
Angstrom works mostly with opie, however, keys aren't right (this will be a common theme) Other than that, it works. Networking can be used via the CF slot. Though there isn't a web browser I've gotten working on opie, so I'm not using it. It by far has the best keymap, but even that lacks, as the numlock doesn't work.

X11 (GPE)
Similar situation with opie, though the keymap is also messed up, there are no numeric keys, Fn+ doesn't even work.

Zubuntu:
Using 1.1 (I think, 9.04 based) and the same 2.6.29 kernel most things work, as configured, it will boot such that the touchscreen is rotated in an odd way. Prior to booting, you need to copy /etc/keymap-2.6 from angstrom. You must logout from X. Then run ts_calibrate. The keymaps are messed up badly in X. I have not managed to generate one that works. Currently, I'm messing with Shepard's, which is fairly close, resulting in most keys being displaced one right or left.

According to some people in #ubuntu-arm, 9.04 is the last version for which it might work on armv5, without some serious recompiliation, which they said would take months. (I found that surprising, given how any other build system (gentoo, OE) I'm familiar with would give a usable system within at MOST a week, on anything relatively modern. They seem to have a problem with cross compilation, or something, it wasn't very clear.)

I've tried emailing the guy (cortez) whose blog is omegamoon, unfortunately, I haven't gotten any response. This, if I could get it working, might well be the best way to go.

Sharp ROM:
Works mostly, and what I've mostly been using, due to the usb bug. I have not tried X/Qt.

I'm mostly on freenode IRC as James_L, and frankly, I'd love to help or have other people with tosas help me.

I'd love any thoughts others have.